cross-posted from: https://piefed.social/c/piefed_meta@piefed.social/p/2603915/piefed-v1-9-is-released-shared-blocklists-auto-bans-and-totp
New features
- Shared blocklists - these are like feeds except instead of listing communities to join it lists people to block. To to Account -> Blocklists to find this feature. Changes by the blocklist author effect all the people who subscribe to the list, causing them to block the list members. They federate, so you can subscribe to blocklists on other instances.
- Edit comments inline, without loading a separate page - wjs018
- Fediverse statistics at https://piefed.social/statistics
- 2-factor authentication (TOTP) - can be added to your account in the ‘Security’ page in your settings.
For admins
- Auto-ban based on the bans that instances you choose, with keyword matching on the ban reason. Go to /admin/users/auto_ban. Try putting ‘piefed.social’ in as the instance and ‘spam’ as the keyword filter. It’ll cut down on the work involved in running your instance SO much.
- Voting pattern graph on user profiles to help spot automated voting.
- Reset the password of any user.
- Lots of inauthentic behaviour reports for finding bots and serial downvoters, see /admin/votes and PM me for an instructional video. It’s a lot to take in but the video will explain it all.
API
- edit matrix user id when saving user profile data.
- scheduled post endpoints - wjs018
Plus a lot more bits and pieces, browse the list of recent releases in the 1.8.x line at https://codeberg.org/rimu/pyfedi/releases for details.
To upgrade from 1.8.x or earlier
git pull
git checkout v1.9.x
Then,
./deploy.sh or ./deploy-docker2.sh
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.


People complaining about shared blocklists and autobans don’t really get the philosophy of PieFed. It’s clearly very opinionated on particular moderation practices that many other people would consider questionable. That’s fine, that’s the devs prerogative. If you like it, use PieFed, if you don’t, don’t.
The thing about PieFed now making equivalent features that are seemingly intentionally incompatible with the PyLova fork though… that seems suspiciously deliberate to break federation between the platforms. This goes against the entire fediverse idea. That is what I would question more (though I don’t know the details of the incompatibility).
People are pointing out the flawed philosophy of piefed. It’s explicitly designed with a singular person’s vision.
The issue is people are happy to ignore that completely and would rather attack those pointing it out than admit the issue.
Then there’s the piefed dev acting like the victim for their own terrible decisions and attacks on others.
I can’t interact with them because they call me out on my bullshit
I can’t work with or communicate with the PyLova people. I have too much trauma from the bullying campaign they continue to operate.
I’m giving away code. It’s a gift. Giving that gift does not put me under any obligations including talking with anyone else, especially not with groups which attack me and disparage me whenever they can.
The way I build PieFed is not intentionally incompatible with Pylova - that happens as a side-effect of me not talking to them and me never looking at their code.
Isn’t that your first rule? Yet your here doing exactly that while still attacking them?
Which is incompatible from what was said by you in just August
https://join.piefed.social/2026/08/14/did-piefed-steal-code-from-pylova-lets-look-at-what-happened/