This is our biggest release yet, including more finished tasks than any of our previous ones. Below is a summary of the highlights:
What’s new
Posts & communities can be labelled as AI-generated and people can choose to hide all posts tagged that way. Very similar to how NSFW works.
Comments can be marked as an Answer, like on StackOverflow.
React to posts and comments with an emoji.
Hide an individual post from yourself, without blocking the author.
PieFed is now in the Yunohost app store, making initial setup easier.
When banned from a remote instance you cannot make local-only posts in their communities.
Honeypot to automatically IP ban badly-behaved crawlers.
https://lemmy-federate.com/ integration, making PieFed communities get more exposure.
“Share on Mastodon” menu item on posts.
Vastly improve docs for new developers, see https://codeberg.org/rimu/pyfedi/src/branch/main/docs/developer_docs.
Language selection is more visible during post creation.
Tag clouds can also be viewed as a list of tags.
View post/comment markdown.
Bot accounts are not included in community statistics.
Footnote support in markdown.
Polish translation.
Better HTTP caching, which reduces dependence on Cloudflare.
Bugs
Passkey fixes.
Polls can now have up to 15 options.
User profile performance improved.
Don’t allow bypassing minimum username length and post title with whitespace.
Polls and Events can no longer be posted into Lemmy communities.
API
Additional user settings can be set through the api, including Extra Fields.
Fetch url metadata.
Sort comments by controversial.
Comment search now works.
Hashtags.
Events.
Polls.
Emoji reactions on posts and comments.
See https://piefed.social/c/piefed_api for more details.
To upgrade
To upgrade from 1.3.x:
git pull
git checkout v1.4.x
./deploy.sh or ./deploy-docker.sh
There is a big database migration that will take a few minutes to run. How long will vary depending on how old your instance is - older instances will have more content to process. It took ~25 minutes on piefed.social so expect it to be less than that.
Donations
PieFed is free and open-source software while operating without any advertising, monetization, or reliance on venture capital. Your donations are vital in supporting the PieFed development effort, allowing us to expand and enhance PieFed with new features.
I think PieFed should allow disabling down-votes. I genuinely dislike seeing down-votes, especially on my own content. I behave very differently on platforms like Bluesky that only have like/repost, compared to Lemmy, where saying something unpopular results in down-votes that feel like a punch in the gut. In real life, if someone disagrees, they either tell you or disengage. On PieFed, down-votes go further, they actively suppress your voice so others don’t see it. That is effectively what down-votes accomplish, and I don’t think it leads to healthier discussion.
I understand that some people find downvotes especially difficult. We should make it easier to find downvote-disabled instances by including this in the instance chooser system.
For me, having the option of doing a downvote (instead of feeling compelled to enter into an unproductive discussion) is what enables me to disengage and overall I see them as a massive benefit.
You mean hiding them for the user?
Or allowing instances to disable them? Because I think it already does - piefed.blahaj.zone.
This should be a user setting. Finding an instance is already hard enough with all the politicking and bans between instances. It shouldn’t be made even harder by turning these into instance-level settings instead of user-level ones.
I mean it is already an instance-level setting, some instances disable them and thus downvotes do not count on their instance.
But are you suggesting you want users on any instance to be able to toggle them of, ie hide their visibility? And further, when you say hiding them - do you additionally mean also negating their impact for the user when they browse their feeds?
Woah, that’s a huge update! Thanks for all of hard work you all have put into piefed :)
@rimu@piefed.social how are the emoji reactions federated? Just as a
Likewith asummaryproperty or something like that, where the emoji is saved? (I think misskey does it that way)Yes, exactly; it’s a like with an
"emoji": "string"attribute. It’s described in the post announcing the feature. :)Oh I missed that, thanks for the clarification 👍
Thank you so much!
Lots of cool features and improvements!
I will need to add a monthly donation thing from next month. I have several organizations that I support on Patreon, but I am curious about LibrePay (really hoping they are not based in the US).
I really like giving with Liberapay! Puts me in full control, gives me a great overview over what I give to different causes, and never bothers me.
All my monthly or weekly donations are actually yearly or in some cases even biannual, in order to minimize transaction costs. But that’s of course a matter of preference.
Thanks!
LibrePay denominates everything in Euro so I guess it’s not US-based.
They are a non-profit in France. I’ve been donating there for years, still very small but working well. The main difference to Patreon is that “creators” cannot message you or send you updates, so you won’t hear back until it’s time for the next payment. And you usually pay for many months in advance.
(They used to do micropayments, but that didn’t work because of fraud detection. I find it interesting how they can still distribute payouts over a team despite this.)
Vastly improve docs for new developers
If there are any curious folks out there that have a familiarity with python, I am the one that authored the new docs for developers interested in contributing to PieFed. Additionally, one of the guides I wrote is about theming PieFed in case any of you css wizards out there want to tweak the styling at all.
Feel free to reach out if anything doesn’t make sense!
one of the guides I wrote is about theming PieFed
Uuhh, I somehow completely missed this. Thank you!
Out of curiosity, why did the creators decide to go with phyton+postgres in particular? I didn’t immediately see that in the docs.
I wasn’t around for the project’s creation, only getting involved ~1 year ago or so. However, @rimu@piefed.social did an episode of Fireside Fedi where he talked a bit about this (~24:00 for rationale about the tech stack and ~33:00 for why python specifically).
Pretty cool update, the emoji reacts are fun and I can see how marking as answer would be useful!
I feel like there’s a risk of abuse though - I could totally see myself replying to certain things with a 🤡 rather than engaging in a debate, and I’m not sure that’s healthy for online culture.
Any emoji also does an upvote at the same time so you’d be upvoting something you dislike. Heh.
This should probably be clear in the UX - right now it looks like I can downvote and emoji you at the same time, even though that’s probably not the case behind the scenes. In a way that risks people accidentally upvoting and giving attention to bad content - I guess I’d personally (in a moment of weakness) throw the 🤡 at leninists or trumpists, voiced I wouldn’t want to amplify.
Also - I was confused about some emojis not working, and then I realized they were tabs and that only the buttons below are emojis. Guess it proves how no UX is idiot proof. Also thumbs up is not under the tab illustrated with a thumbs up, which is confusing. :)
Yes, still lots of rough edges. I expect that reactions and votes will be decoupled in future.
The thumbs up shows a pane of commonly used emoji, I wasn’t sure what to use to indicate that. Then, to make it more confusing, I left out ‘thumbs up’ from that pane because people can just upvote to indicate agreement. 🥴️
Be the change then?
I’ll try to resist myself, but I think expecting people to behave themselves is a pretty tall order for social media. :/
Sure, you can’t control people, but can you control yourself?
I think designing good social media is largely about identifying and removing possible abuse vectors. So if think it’s relevant to point it out when I see potential for one. My comment was not really about myself, whatever the hell I do is not very important.
Impressive list, thank you to everyone involved!
Hide an individual post from yourself, without blocking the author.
Wooowwwww. Sweet! Thank you
Wow, I missed it, great!
That issue was one of yours, thanks for bringing it up!
as a bullet list
What’s new
- Posts & communities can be labelled as AI-generated and people can choose to hide all posts tagged that way. Very similar to how NSFW works.
- Comments can be marked as an Answer, like on StackOverflow.
- React to posts and comments with an emoji.
- Hide an individual post from yourself, without blocking the author.
- PieFed is now in the Yunohost app store, making initial setup easier.
- When banned from a remote instance you cannot make local-only posts in their communities.
- Honeypot to automatically IP ban badly-behaved crawlers.
- https://lemmy-federate.com/ integration, making PieFed communities get more exposure.
- “Share on Mastodon” menu item on posts.
- Vastly improve docs for new developers, see https://codeberg.org/rimu/pyfedi/src/branch/main/docs/developer_docs.
- Language selection is more visible during post creation.
- Tag clouds can also be viewed as a list of tags.
- View post/comment markdown.
- Bot accounts are not included in community statistics.
- Footnote support in markdown.
- Polish translation.
- Better HTTP caching, which reduces dependence on Cloudflare.
Bug Fixes
- Passkey fixes.
- Polls can now have up to 15 options.
- User profile performance improved.
- Don’t allow bypassing minimum username length and post title with whitespace.
- Polls and Events can no longer be posted into Lemmy communities.
API
- Additional user settings can be set through the api, including Extra Fields.
- Fetch url metadata.
- Sort comments by controversial.
- Comment search now works.
- Hashtags.
- Events.
- Polls.
- Emoji reactions on posts and comments.
- See https://piefed.social/c/piefed_api for more details.
PieFed v1.4.0 is free and open source. Nice, my instance is already up to date.
Amazing work! Thank you for all of the effort that was put into this!
ohh I need to update my yunohost!
We’ll have to wait a bit for YunoHost to do their thing
Awesome work, much appreciated!
Is it possible to turn off the lemmy-federate integration? Or better keep it disabled by default?
This tool has a lot of unintended bad side effects, both culturally and technically in regards to horizontal scaleability of the federation that I think it does more harm than good.
I believe that to make lemmy-federate do it’s thing an instance admin needs to go to lemmy-federate.com and enroll their instance. Without doing that, nothing happens.
This is correct. You even have to manually add DNS records for it to work.
It’s opt-in, the same way it is for Lemmy
















