What’s new
- Media library that lets you upload images to comments/post body and paste from the clipboard
- Animated gif support for user profile pictures
- Specify alt-text for link posts that link to an image
- Emoji picker and spoiler button added to markdown toolbar
- More links to the modlog (footer, community sidebar, user profile) and improved searching/filtering
- Leave a conversation to remove it from the list of their direct message conversations
- Post urls are now “friendly” since they include the community name and a snippet of the title instead of just a number
- Add link to show parent comment when directly viewing a comment reply
- Image markdown style formatting to allow more advanced control of how images are rendered. e.g.
 - Code syntax highlighting in code blocks and allow for style selection in user settings
- Tag cloud added to sidebar for feeds and topics
- Better searching and filtering of the Instances list
- Add a block (of a user, community, instance or domain) from the blocks and filters management area, without doing it via a post
- Popup suggestions when mentioning a community or user as you type
- Onboarding plugin which auto-subscribes, auto-blocks and sends a welcome message for new accounts
- Improved federation efficiency
- Old posts can be automatically archived (saved to S3) to free up database space
- Old posts by bots with no comments are automatically deleted
- LLDAP support, which does LDAP a bit differently
To upgrade
To upgrade from 1.2.x:
git pull
git checkout v1.3.x
./deploy.sh or ./deploy-docker.sh
In the past we had a separate project for realtime notifications, which is now unsupported as it’s code has been merged with the main PieFed project. To set it up, refer to the Push Notifications section of install.md. As well as enhancing the user experience doing this will decrease load on your server if it hosts local communities with many subscribers as some of the federation work has been offloaded to the push notifications service.
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.
Looks like some pretty solid improvements (I use piefed on a different account).
Looking forward to checking out the image upload functionality and the UI/UX improvements.
Post urls are now “friendly” since they include the community name and a snippet of the title instead of just a number
It’s good that the old style links aren’t broken.
The old style links still work in my experience
https://anarchist.nexus/ already upgraded
Their theme broke with the update?
Looks fine here. Maybe cached resources in the browser? They’re also on cloudflare, that’s another level of cache that might not have cleared.
just upgraded my instance. pretty good, very smooth and yay animated profile avatars!
Cool!
Image markdown style formatting to allow more advanced control of how images are rendered. e.g. 
You might as just let users write the
<img>tags directly at this point, at least then you won’t add noise to third party apps’ accessibility stacks.(I honestly wouldn’t be opposed to letting users write HTML directly, it was one of Tumblr’s best features imo)
Tried to setup it once bare metal, everything prepared, but only got an error on db init…
flask db upgradeworked butflask init-dbonly threw cryptic errors…The docs on join.piefed.social are very limited, they should refer to those on Codeberg. Codeberg docs were completely missing how to setup S3 storage. I just took a look, now it is in the docs. This is good 👍🏻
While I set up piefed, you read in the middle of the docs, that you need a second project for notifications at the time I tried to set this up.
Now you don’t need it anymore, as far as I read in the docs.
“Okay just use Docker…”
Multiple cronjobs for containers? Come on 😐 Lemmy is far easier to use in a container.
Maybe a take look at piefed again when there is a background manager instead of 4 cronjobs.
I’ve never used the baremetal setup, so I can’t speak to that. However, I actually agree with your points on the docker deployment. It’s something I have spoken about to some length with people in our matrix channel as well. There are a couple things that I don’t love about the current docker setup process, but just don’t know docker or linux stuff well enough to fix:
- Needing to set up external cronjobs like you mentioned
- Needing to exec into the container for initial setup
- Not having pre-built containers that we can put in a container registry to make things easier
Docs are an always evolving thing and we have been fortunate enough to have some other admins go through the setup process and provide feedback, which has helped flesh the docs out some more. However, there is always more that can be done.
I see your efforts in the last months. My test failed about 5 months ago, but I will give it another try with the bare metal setup in future.
Piefed is actually the only serious alternative to Lemmy in my opinion. Hope you find help with the container, it is the most used way to selfhost these days, wish you the best :)
mbin:


In terms of number of users, rate of growth (in number of users, communities, instances, etc.), level of app support, appreciation from the Threadiverse community, and by all other metrics, yeah? Especially the sheer pace of development of PieFed, which is just a pleasure to observe such a labor of love.
Threaded conversations in Mbin appear more like an afterthought to the Twitter/X microblogging style - see e.g. its own level of app support. Also, the peak of Mbin (according to this site was 874 monthly active users in April 2024, but just one month later that had dropped to 563 and today is 719.
Though Mbin is still remembered - now as the Threadiverse = Lemmy + PieFed + Mbin (+ nodeBB + flarum, with Sublinks seemingly abandoned). There is room for us all here! :-) I will add that if Mbin ever wanted to actually get serious, it would be nice to see.
Such a great update. Huge thanks to the team!










