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 6 points 5 days ago

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.

[-] Blaze@piefed.zip 4 points 5 days ago

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.

[-] AwesomeLowlander@cozyver.se 7 points 5 days ago

You have to admit, deliberately breaking compatibility with Pylova's identical blocklist feature isn't the best look though.

[-] y0kai@anarchist.nexus 7 points 5 days ago

lol nothing Rimu does is "a good look"

[-] TragicNotCute@lemmy.world 0 points 4 days ago

Please be respectful. Personal attacks aren’t appropriate for this community.

[-] y0kai@anarchist.nexus 5 points 4 days ago

I agree, with the added caveat that respect is a two-way street.

[-] goferking0@lemmy.sdf.org 3 points 3 days ago

I'm still confused how it's an attack to point out whats happening 🤷

[-] y0kai@anarchist.nexus 3 points 3 days ago
[-] goferking0@lemmy.sdf.org 1 points 3 days ago

Bad enough that saying it is enough to have instance admins pleaded too to ban said users

[-] TragicNotCute@lemmy.world 1 points 4 days ago

When Rimu comes in this community and starts talking about how you specifically are a problem, report their ass and I’m on the case.

[-] pinto@lemmy.world 2 points 1 day ago

We have, you're not doing your job. Have you read Null's posts here?

[-] goferking0@lemmy.sdf.org 4 points 3 days ago

You mean like null is doing in the thread?

[-] Blaze@piefed.zip 3 points 4 days ago

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".

[-] AwesomeLowlander@cozyver.se 3 points 4 days ago

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.

[-] Blaze@cozyver.se 4 points 4 days ago

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

[-] arules@retrofed.com 1 points 4 days ago

Here, let me help you reframe the miscommunication:

As it stands doing nothing is only harmful for PyLova [which] has it’s unique features [incompatibility broken] at each step [piefed development implements their version].

lemmy,{k,m}bin, et al. can implement these features pylova compatible too. Piefed refuses to compatibilize.

[-] Blaze@piefed.zip 3 points 4 days ago

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?

it’s clearly an attempt to try to ensure PyLova cannot gain traction with its own unique feature sets.

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.

[-] arules@retrofed.com 2 points 4 days ago

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.

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

The past commits have been reverted, haven't they? https://join.piefed.social/2026/08/14/did-piefed-steal-code-from-pylova-lets-look-at-what-happened/

And yeah, time will tell for the rest

[-] null@piefed.nullspace.lol -1 points 4 days ago

deliberately breaking compatibility

Source?

[-] goferking0@lemmy.sdf.org 3 points 4 days ago

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

[-] null@piefed.nullspace.lol -3 points 4 days ago

What do you mean I "won't acknowledge it"?

Are you defending @awesomelowlander@cozyver.se 's claim?

[-] goferking0@lemmy.sdf.org 2 points 4 days ago
[-] null@piefed.nullspace.lol -3 points 4 days ago* (last edited 4 days ago)

I mean, I definitely proved a point.

[-] goferking0@lemmy.sdf.org 1 points 4 days ago

Unable to read rimus comments or just reading in general?

Or confusing users?

Or just attacking anyone who has actual evidence and thought processes?

[-] null@piefed.nullspace.lol -2 points 4 days ago

Look at you, now continuing to prove my point.

[-] AwesomeLowlander@cozyver.se 0 points 4 days ago* (last edited 4 days ago)
{
  "@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.

[-] null@piefed.nullspace.lol -3 points 4 days ago

Are you going to share your source for your claim of "deliberately breaking compatibility"? Pretty strong claim...

[-] AwesomeLowlander@cozyver.se 1 points 4 days ago

There are 3 possibilities:

  1. By accident. That would mean Rimu didn't know about the existence of Pylova's blocklist feature. Lets not go down there.
  2. Forced / without choice. Because he wasn't capable of doing it, or somebody held a gun to his head.
  3. Deliberate. He made a conscious choice to do so. Whether because he felt another approach was preferable, easier, w/e.

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.

[-] null@piefed.nullspace.lol -3 points 4 days ago

I notice you have once again failed to provide any source for your strong claim. I think at this point we can assume you made it up.

Gee, who could have predicted the exact crybullies rimu was talking about who show up to tell lies about him any time PieFed is mentioned would show up and tell lies about him!

[-] AwesomeLowlander@cozyver.se 2 points 4 days ago

At this point I'm not sure you even read my comment... WHAT strong claim? Would you like to take a look at my previous comment and tell me which of the 3 possibilities you think was the case?

[-] null@piefed.nullspace.lol -4 points 4 days ago

WHAT strong claim?

You made the strong positive claim that rimu deliberately broke compatibility with pylova.

I've asked you twice now for your source for that claim. You've instead given me other scenarios you imagine could be the case if it wasn't true that rimu deliberately broke compatibility.

That's completely non-responsive to my question... No one asked what you imagine might have happened.

[-] AwesomeLowlander@cozyver.se 2 points 4 days ago

So the comment that somebody else linked an hour ago, that you replied to, direct from Rimu, isn't enough? Or are you being deliberately facetious here?

https://lemmy.world/comment/26882650

Do you understand the meaning of the word deliberate?

[-] null@piefed.nullspace.lol -2 points 4 days ago* (last edited 4 days ago)

That comment doesn't demonstrate whatsoever that rimu "deliberately broke compatibility with pylova".

Do you understand the meaning of the word deliberate?

Of course I do. Do you? How about the word "break"?

Edit: Do you think deliberate means "not intentional"?

[-] AwesomeLowlander@cozyver.se 2 points 4 days ago

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?

[-] null@piefed.nullspace.lol -2 points 4 days ago* (last edited 4 days ago)

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?

No, I just thought you might also not know what that meant. Looks like I was right.

Rimu deliberately chosing to not be compatible with Pylova’s identical blocklist feature isn’t the best look though.

Source for rimu "deliberately chosing to not be compatible with Pylova"? Your previous source was about rimu not intentionally choosing to be incompatible with Pylova. Which is, of course, the exact opposite of your claim.

[-] AwesomeLowlander@cozyver.se 2 points 4 days ago

No no, I'm done. Thank you for providing a good show for everybody else.

[-] null@piefed.nullspace.lol -3 points 4 days ago* (last edited 3 days ago)

No no, I’m done.

And it's extremely obvious why.

Thank you for providing a good show for everybody else.

Thank you for demonstrating in real time how you guys lie to push a narrative.

Edit: I'll say for anyone reading -- these guys never say things like "it's a shame rimu didn't make this compatible with pylova" or "rimu should have done his due diligence to make sure this was compatible with pylova".

They just go straight for boldfaced lies. They link to the same comments to push the same narratives. There's a reason they do this. Keep an eye out for it. You'll see the same names a lot.

Another one of the usual suspects. Can you imagine how much they would kick and scream if someone mocked them for expressing trauma. They have no standards:

UjES6jcZd3VTNxd.png

[-] fediverse_fremont@lemmy.world 3 points 3 days ago

“it’s a shame rimu didn’t make this compatible with pylova”

After reading this thread (like an idiot, holy shit) I gotta say: Not making it compatible when he knew the other code existed was a choice. A deliberate and intentional one.

“rimu should have done his due diligence to make sure this was compatible with pylova”

Choosing not to do due diligence to make it compatible was also a choice, especially when they already know the feature exists on the other site. Was it a malicious choice? A lazy choice? I don't care and only they know. It was still a choice though and choices are deliberate.

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.

Willful ignorance is always a choice. He claims it is not "intentionally incompatible" and then goes on to say that he intentionally makes no attempts to make it compatible which to me sounds a lot like doublespeak.

I won't be replying because everything I've seen from you is in bad faith. You argue like a republican.

[-] goferking0@lemmy.sdf.org 1 points 3 days ago

I won't be replying because everything I've seen from you is in bad faith. You argue like a republican.

Oh that's perfect. I'm using that tyty

[-] null@piefed.nullspace.lol -1 points 3 days ago* (last edited 3 days ago)

As though you needed more one-liners to use when you cop out of an argument you're losing.

Edit: Oh look at that, you did exactly what I said you would, immediate, in multiple places!

You have to be a gag-account. There's no way you're serious.

[-] goferking0@lemmy.sdf.org -1 points 3 days ago

I won't be replying because everything I've seen from you is in bad faith. You argue like a republican.

[-] null@piefed.nullspace.lol -1 points 3 days ago* (last edited 3 days ago)

After reading this thread (like an idiot, holy shit) I gotta say: Not making it compatible when he knew the other code existed was a choice. A deliberate and intentional one.

Intentionally choosing to disengage from Pylova and its developments? Sure. That's also a fair thing for him to do.

Choosing not to do due diligence to make it compatible was also a choice

Easy there, Geddy Lee.

I won’t be replying because everything I’ve seen from you is in bad faith. You argue like a republican.

No, you won't be replying to me because you've seen how good-faith I am and how I expect good-faith from others and you just want to torture the English language.

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

Fediverse

45015 readers
132 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