115
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.
Oh it only took 5 comments for you to narrow down what your actual issue with my statement is. So your objection is to my usage of the word 'break', then? Nothing else? Why didn't you say so 4 comments ago? And not after you conclusively lost the argument on deliberate?
Rimu deliberately chosing to not be compatible with Pylova’s identical blocklist feature isn’t the best look though.
Better?
No, I just thought you might also not know what that meant. Looks like I was right.
Source for rimu "deliberately chosing to not be compatible with Pylova"? Your previous source was about rimu not intentionally choosing to be compatible with Pylova. Which is, of course, the exact opposite of your claim.
No no, I'm done. Thank you for providing a good show for everybody else.
And it's extremely obvious why.
Thank you for demonstrating in real time how you guys lie to push a narrative.