143
PieFed v1.9 is released - Shared Blocklists, Auto-bans and TOTP
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.
Comments
Worse than reddit. Almost feel like China ranking system
For what it’s worth, China never had a social credit system. They introduced a regional credit system targeting businesses to counter fraud and corruption, and some western tabloids reported on it like it was some Orwellian nightmare, and then major news stories picked the tabloids up and acted like they were legitimate. Here’s a good article on the subject. The US’s credit score is far more consequential and invasive than the regional credit system they partially introduced in China.
Maybe an unpopular opinion, but I have mixed feelings about the social/community implications of shared block lists.
It’s essentially social blacklisting, and while it gives people more options for controlling what they see, I’m not entirely convinced it’s healthy compared to manual blocking of users and servers on an individual level.
Social blacklists are literally never under any circumstances good. They have always and will always result in abuse and problems.
It really helps communities of people who get harassed regularly. This feature not being on mastodon was a big reason the blacksky community formed based on bluesky. They tried fedi first but desperately need these types of controls to keep from getting called slurs.
Actually kind of funny that your comment and another right under you are kind of like the same reasoning from both sides. Like one doesn’t want the furrys harassed and one doesn’t want to know the furrys exist. So ig the block list thing is not the worst?
I don’t even see the comment about not wanting furries to exist. So i guess somewhere, a block was successful!
We really need general purpose lists that can be either block or follow. That way everyone can use the same furry list and be happy.
I like where your head is at
I think it’s way healthier than the uninvited community mixing that comes from automated post merging. There’s already a pretty significant ideological bent against moderating communities on the threadiverse; this is just an opt-in tool to counter the entitlement to an audience.
Yes I expect it will be a mixed bag. But we all know how much blocking new people need to do to make this place livable so hopefully this will help people get to that state quicker.
I don’t feel that strongly about it. I think I just blocked Lemmy.ml and dbzero or whatever the hell it’s called.
[removed by a moderator]
Why did you block those?
Yes blocking whole instances is pretty efficient.
This feature might not end up getting used much. That happens a lot but until we try it we won’t know. But it’s a pretty big thing on a lot of platforms, like Bluesky, so I think it’s worth a try.
If the user can make named blocklists, that sounds like a good idea to me. If it’s just “you can also block all the same people I do” then I am kind of thinking the same thing you wrote here
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).
Not doubting you because I am not following development of neither very closely, but what would be an example of “intentionally incompatible” features?
I don’t really know either, I was commenting on some other comments that mentioned it elsewhere in this thread.
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
It promote sheep mentality. I have my own brain to decide what I want to block and not blindly follow a blocklist
That’s great! I personally agree with you. The fediverse is so nice that you can simply choose not to use PieFed in that case, and the people who do prefer that sort of feature can choose to use PieFed if they desire. Everyone is happy.
Lemmy and piefed can interact with each other so the blocklist could also include lemmy users. Sheep mentality is bad, how many people who use those block list will investigate if all users really fit in that block list. Aboiding talking about problems do not solve the problems.
If a PieFed user blocks a Lemmy user because of a shared blocklist from another PieFed user, then that’s the PieFed’s users own choice for doing that. If they didn’t want such a shared blocklist functionality, they could just not use PieFed. Are you going to tell them that they can’t use an instance with a feature they prefer? That’s not very aligned to the ethos of the fediverse, which is that everyone gets to choose their preferred instance.
I don’t agree with that feature, but I’m not gonna tell other people how to live their lives. If they want shared blocklists, that’s their choice.
That’s the spirit
Do you realize that you can critize things without forcing anybody to do what you believe? What you are doing is toxic posivity where people can’t no longer critisize anything
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.
Literally what the fuck are you on about?
💀💀💀
Pretty sure those pointing out flaws in piefed get more bullying and harassment. But what do I know only have 1 user doing it today to me and another user
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/
Shared blocklists sounds like the kind of nonsense that ruined Reddit
Random subs would persecute you and ban you just because you commented on a post in a sub they didn’t like, even when you never did anything in their sub
It’s ‘guilt-by-association’ nazi BULLSHIT
Giving control over blocks and bans to a 3rd party sounds like a great idea. Especially if you like groupthink.
That is exactly what rimu wants so 🤷
Auto ban sounds terrifying and definitely won’t be abused
I mean, it makes running a smaller instance a lot easier. Maybe read what it actually does and think about why it would potentially be problematic.
Presumably people running small instances would make us of this drawing on moderation efforts from a bigger instance that they trust. It’ll benefit people on smaller or single use instances, but shouldn’t affect the majority of users. Just makes decentralization more painless.
I agree some other name such as “filtered banlist federation” or something could seem less scary as a label than “auto-ban”.
By making it more centralized?
PyLova already had this feature, does PieFeds work with it or is it breaking Fediverse compatibility?
Funny how PieFed gets multiple images in posts, and now in-line comment editing/shared blocklists after PyLova introduces it. Does PieFed have any original ideas?
Sharing of ideas and code is a core tenant of FOSS. PyLova literally started as a copy of Piefed. Why shouldn’t the ideas and features flow both ways?
Multiple images in posts and in-line comment editing are basic features coppied from Reddit (and, like, every social media site), which probably coppied them from somewhere else. Let’s not pretend like PyLova is breaking new ground here, lmao.
These are only being added straight after PyLova does it. And considering Rimu’s hostile history it’s clearly an attempt to try to ensure PyLova cannot gain traction with its own unique feature sets.
And the way they are being added is not compatible with PyLova’s methods. Which breaks Fediverse compatibility. If any software such as Lemmy were to implement it in the future they would most likely ensure compatibility with the larger userbase PieFed model.
This is the similar to Microsoft’s “Embrace, extend, and extinguish” philosophy to kill off the competition.
Do you have any context/source for “Rimu’s hostile history”? Because I’ve tried looking into that a few times but I’ve only ever found this Piefed devlog post which makes Piefed sound reasonable but obviously has every incentive to be biased.
I don’t want to get too off-topic here, so I’ll message you.
May as well start with rimu flat out attacking everyone associated with it again
Hey, I’m not familiar with either implementation - how does PyLova do it? And how does PieFed do it?
why doesn’t @rimu@piefed.social admit that he got the ideas from Mia then? why copy changes from PyLova, and strip attribution, then admit to MrKaplan that he did it so that she wouldn’t be attributed? moth supposes that perhaps he does not want to admit Piefed is inferior to PyLova.
no, but PyLova IS doing most of the dev work for Piefed.
How come pylova isn’t publishing these updates here too?
It is?
https://quokk.au/c/fediverse@lemmy.world/p/1281812/pylova-v0-5-0-shareable-blocklists-roles-ui-changes
https://quokk.au/c/fediverse@lemmy.world/p/1237518/pylova-v0-4-1-customisation-performance-qol-bugs
https://quokk.au/c/fediverse@lemmy.world/p/1214229/pylova-v0-4-0-moderation-community-management-tools-galore
https://quokk.au/c/fediverse@lemmy.world/p/1135278/pylova-v0-3-2-released-muffles-reels-flags-bookmarks-and-more
https://quokk.au/c/fediverse@lemmy.world/p/1105596/pylova-v0-3-1-released-multi-image-post-support
https://quokk.au/c/fediverse@lemmy.world/p/1092867/pylova-v0-3-0-released
https://quokk.au/c/fediverse@lemmy.world/p/1077126/pylova-v0-2-2-released
Interesting. Either I scrolled past it or didn’t know what it was and ignored it.
Is there any history on why it was forked? Could be useful to add to the repo.
according to the PyLova devs, it was forked to remove the hard-coded (at that time) censorship in Piefed, especially the anti-memes censor and upvote punishment. memes are a valued and culturally important form of self-expression, and even if the Piefed author is from an older generation, it doesn’t mean those memes should have to swim upriver just to get the same engagement on Piefed as they do on Lemmy.
If you love pylova so much why don’t you just marry it?
that’s a good idea, thank you! moth thinks marriage is an outdated concept, but moth might find it agreeable if it’s to the best threadiverse software currently available!
I use both, starting another flamewar doesn’t seem positive for either project.
If I don’t call out bad behaviour it will continue. As it stands doing nothing is only harmful for PyLova who has it’s unique features copied at each step.
Is Mia supposed to patent Pylova features, and prevent any other Fediverse software to use them, be it Lemmy or Mbin? Serious question, as otherwise I don’t see how this can be solved.
Features have always been replicated between software, even beyond the Fediverse.
You have to admit, deliberately breaking compatibility with Pylova’s identical blocklist feature isn’t the best look though.
lol nothing Rimu does is “a good look”
This is a different question. The comment above is advocating for “Piefed to stop copying Pylova features”, you are speaking about compatibility, which I guess would also be criticized for “copying the feature”.
Source?
Rimu is here making it worse fyi
Please be respectful. Personal attacks aren’t appropriate for this community.
How is describing what they are doing in the thread an attack?
Because it’s your opinion and I haven’t seen Rimu do anything in this community that breaks the rules.
My parents gave me some advice early on in life, maybe you should hear it too.
If you can’t say something nice, don’t say anything at all.
There are numerous places on Lemmy that will happily let you say far meaner or disrespectful things about whoever you’d like (myself included). That’s not how I run this community though.
We are so small haha. Its so silly.
Definitely x)
Its a fork isn’t it? So like 95℅ of the codes the same.
The fork split off 7 months ago, PyLova independently added these features weeks and months before PieFed ever did.
And it has now been confirmed that Rimu has made it non-compatible.
I’ll take a look later. It should have a tiny bit my code in there.
EDIT: So I took a look. If this is the repo:
https://codeberg.org/quokkau/PyLova
Then im seeing piefed code pulled into pylova as soon as Nov 5th. Last week.
It looks more like pylova is pulling from piefed rather than the other way around. I mean this is what open source is for. But it sure looks like rimu did most of the work when you look at: https://codeberg.org/quokkau/PyLova/activity/contributors
By a HUGE factor.
It also looks like piefed has much more active development. So this seems like a silly argument to have by a long shot.
You can clearly see where the project forked and any upstream contributions from Rimu basically stopped existing except for some bug fixes being bought over, of which PyLova has also contributed to PieFed with bug fixes.
image
It does not seem a silly argument to call out a larger project from copying every idea introduced into a rival fork weeks after they introduce it. Why isn’t PieFed coming up with original ideas for what to offer its users? Is the project that devoid of trajectory that it has no idea what it wants to do next.
image
Thank you for having a look
Pylova is built 50% on piefed, 50% on a complete misunderstanding of what open source software is.
Maybe it’s because the PyLova maintainers refuse to let their code be contributed back, loosing their shit and accusing Rimu of stealing instead of contributing their code back.
Rimu is welcome to bring over PyLova code, he only needs to attribute it instead of deliberately removing the author from the work as he did last time and has been well documented in his conversation with others admitting trying to do.
Did he really though? For the main code including the patch file should have preserved the author for the commit, right? As is shown in the blog post. Honestly that is enough to meet the license requirements. I guess you could argue that he skipped it for the themes, but really? Do you still think that warrants the narrative that they’re stealing code? (Which is a fucking rich statement for a fork to accuse the source project of anyway)
It would also have been nice to shoutout in the release notes as well, but we never got to see that because of the drama.
as soon as the fork was made, were the PyLova devs not banned from all Piefed channels? was the first security patch authored by the PyLova devs not ignored by @rimu@piefed.social, despite attempts to reach out so that Piefed could take advantage? tell moth, how long should the PyLova devs continue reaching out, only to have Rimu push them away? why do you have this double-standard?
Yeah that means PyLova copied a lot of features from PieFed lol, that’s how forking works.
It does suck if it’s not all compatible though, I hope that gets figured out
all attempts to reach out to Rimu are shot down by Rimu and the persons blocked or banned from Piefed channels, so moth isn’t sure how things will get “figured out”.
Becareful this will get called a attack
Yes and forks give attribution. They essentially say, “this is a fork of this other program. It is made with a lot of the other program’s code. We wouldn’t exist in our current state without using the original codebase as a starting point.”
Whereas Rimu has a history of behavior which shows his thoughts are more along the lines of: “This is mine. Someone else came up with the idea and wrote it, but their contributions aren’t contributions because I don’t like them and so they don’t deserve credit.”
It wouldn’t be so bad if Rimu had actually copied the code, which would then be compatible. Or even implement his own code in a compatible way, if attributing PyLova’s devs is such a taboo for him. But he chose to implement a non compatible feature, fomenting fragmentation and a worse user experience. And for what?
All I want is to be able to view my upvoted and downvoted content in voyager and Alexandrite.
Yay totp
Sign in to comment. Sign in