145

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.

Donations can be made via Patreon, Liberapay or Ko-fi.

you are viewing a single comment's thread
view the rest of the comments
[-] CobraCommander@quokk.au 13 points 5 days ago* (last edited 5 days ago)

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.

[-] mesamunefire@piefed.social 9 points 5 days ago* (last edited 4 days ago)

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.

[-] CobraCommander@quokk.au 5 points 3 days ago

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

[-] Blaze@cozyver.se 5 points 3 days ago

Thank you for having a look

[-] cabbage@piefed.social -1 points 3 days ago

Pylova is built 50% on piefed, 50% on a complete misunderstanding of what open source software is.

[-] SirHaxalot@nord.pub -4 points 4 days ago

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.

[-] CobraCommander@quokk.au 10 points 4 days ago* (last edited 4 days ago)

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.

[-] SirHaxalot@nord.pub -2 points 4 days ago

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.

[-] CobraCommander@quokk.au 11 points 4 days ago

image

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.

[-] moth@anarchist.nexus 7 points 4 days ago

the PyLova maintainers refuse to let their code be contributed 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?

this post was submitted on 15 Nov 2026
145 points (94.5% liked)

Fediverse

45015 readers
177 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, Mbin, etc).

If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!

Rules

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration)

founded 3 years ago
MODERATORS