this post was submitted on 15 Nov 2026
113 points (95.9% liked)

Fediverse

44949 readers
322 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
 

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
[–] AwesomeLowlander@cozyver.se 7 points 11 hours ago (3 children)

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

[–] y0kai@anarchist.nexus 6 points 10 hours ago

lol nothing Rimu does is "a good look"

[–] null@piefed.nullspace.lol -1 points 6 hours ago (2 children)

deliberately breaking compatibility

Source?

[–] goferking0@lemmy.sdf.org 1 points 1 hour ago (1 children)

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 0 points 53 minutes ago (1 children)

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

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

[–] goferking0@lemmy.sdf.org 1 points 20 minutes ago (1 children)
[–] null@piefed.nullspace.lol 0 points 9 minutes ago

I mean, I defintely proved a point.

[–] AwesomeLowlander@cozyver.se 0 points 1 hour ago* (last edited 1 hour ago) (1 children)
{
  "@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 0 points 55 minutes ago (1 children)

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

[–] AwesomeLowlander@cozyver.se 0 points 35 minutes ago (1 children)

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 0 points 14 minutes ago (1 children)

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 0 points 11 minutes ago (1 children)

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 0 points 6 minutes ago (1 children)

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 0 points 1 minute ago (1 children)

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 1 points 31 seconds 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"?

[–] Blaze@piefed.zip 0 points 8 hours ago (2 children)

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 1 points 28 minutes 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.

[–] arules@retrofed.com 1 points 7 hours ago (1 children)

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 1 points 7 hours ago (1 children)

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 6 hours 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.