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.



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.
Hey, I’m not familiar with either implementation - how does PyLova do it? And how does PieFed do it?
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
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.
Anti-memes censor and upvote punishment? Is this real? 😂
yes, although after quite a bit of backlash, he apparently added a switch to turn off most of it. it seems that Rimu does not like memes, judging by the fact he added several functions to suppress them. things like marking meme comms “low quality”, making upvotes count less than on other posts, etc. those functions have been removed in PyLova for obvious reasons. memes are fun, and they are culturally relevant to millennials and Gen Z. and while it’s true that older generations like Rimu might not appreciate them as much, they shouldn’t be quietly punished without telling anyone.
Good to know. I guess if I ever sign up to another instance, it’ll be a pylova instance, not a piedfed one.
So the thing about autobans and shared blocklists… they help suppress knowledge about that stuff getting around.
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”
Please be respectful. Personal attacks aren’t appropriate for this community.
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”.
I’m only pointing out the optics of it aren’t great. I do agree Pylova doesn’t have a monopoly on a feature just because it implemented it first.
Yeah, it’s definitely not great. At the beginning of this thread, I was hoping some dialog could be established to agree on comparability for the blocklist, but seeing how it went, I don’t think it will happen.
I’m trying to stay neutral on the whole thing. I like both Piefed and Pylova, and it feels a bit like having two friends who don’t talk to each other.
Anyway, I’ll get back to subscribing some communities to cozyver.se
Here, let me help you reframe the miscommunication:
lemmy,{k,m}bin, et al. can implement these features pylova compatible too. Piefed refuses to compatibilize.
That’s what I was addressing. According to that logic, even if Piefed supports blocklists the way Pylova does it, then it’s still preventing Pylova to gain traction with its own unique featue sets.
Maybe I’m missing something.
In the case of popularity, @cobracommander@quokk.au is correct in this assessment, as Piefed refuses to acknowledge 1) pylova or 2) accredit original pylova features. I don’t want to partake in that discussion.
Legally, piefed has to accredit any code it copies, which piefed devs have not done so in the patch demonstrated before. These current implementations maybe legally different. I have not compared them yet.
In libre ethics, breaking compatibility with an early implementer of a feature in a shared network maybe coincidental, or in the case CC argues, anti libre. Piefed devs are aware of this thread, and read the contents. Now it’s a matter of when piefed users desire to pylova compatibilze these features. Time will tell.
Source?
You won’t acknowledge it but for everyone else here’s rimu saying well it’s just unfortunate and their fault totally nothing I did
https://lemmy.world/comment/26882650
What do you mean I “won’t acknowledge it”?
Are you defending @awesomelowlander@cozyver.se 's claim?
Ty for proving the point
{ "@context": "...", "id": "https://example.org/blocklist/general", "type": "OrderedCollection", "name": "General Blocklist", "summary": "Description of the list", "attributedTo": "https://example.org/u/admin", "published": "...", "updated": "...", "totalItems": 2, "first": "https://example.org/blocklist/general/entries?page=1", "inbox": "https://example.org/inbox", "visibility": "public", "subscriberCount": 10 }The feature is nothing more than shared basic JSON data. If your thrust is that Rimu is too incompetent to handle that, I don’t really think so, but I can accept that too.
Are you going to share your source for your claim of “deliberately breaking compatibility”? Pretty strong claim…
There are 3 possibilities:
You seem to be conflating ‘deliberate’ with ‘malicious’. Those are 2 separate things. Read my original statement again without projecting any of your assumptions onto it.
Rimu is here making it worse fyi
Please be respectful. Personal attacks aren’t appropriate for this community.
We are so small haha. Its so silly.
Definitely x)
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!
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.
Thank you for having a look
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.
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.
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.
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?
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.
He exported the code as a patch, while not knowing it would make her (correctly) the author. His intention very clearly looks to be as if to use her code without bringing over the authorship. And he did do exactly that later on with copying the themes and renaming it.
So yes I believe that warrants calling out at the time he did steal the code.
I am not saying he stole the code here, I am simply saying he is jacking the new features being introduced in an effort to harm PyLova by making it not be able to stand out with unique features. These are really the only big new user facing features he is adding and it’s conveniently shortly after we do.
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”.
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?
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.”
Probably cause Pylova is vibe coded slop
piefed is too🙃.
…what? No its not…https://codeberg.org/rimu/pyfedi/commits/branch/main its all people. real people.
Plus the code is not in the style AI usually does python.
and it looks like pylova is the same?
https://codeberg.org/quokkau/PyLova/commits/branch/main
did you even read the thread here? Rimu already admitted to using AI to patch a commit into piefed he didn’t even bother to copy and paste under his own credentials. Even OP’s boyfriend admitted to using LLM for his piefed theme.
Both projects use LLM. This isn’t up for debate, but facts.
Your first link doesn’t mention AI at all and your second link is about a separate frontend for PieFed from a separate repo?
Look up the dates of Mia’s pulled patch in the diff… You’ll find Rimu’s output of ChatGPT’s Python.
Which patch? I’m not gonna dig through the whole git history…
… your hypocrisy is outstanding.
Notice Rimu replaced quokkau’s commits for a ghost profile called rimu and consequently, Shadow is ChatGPT..