Defederation - I really need to improve https://piefed.social/instances so it shows the blocked instances. Anything that is a continual moderation headache gets blocked, temporarily or otherwise. This week aaalll the spam is coming from lemmings.world so they’re out but once it dies down they’ll be back. Hexbear and lemmygrad will always be blocked and PieFed is coded to block them by default on all new instances (admins can change it). No plans to defederate lemmy.ml as I’ve built mod tools that help me find the most odious users & banned them and now it’s tolerable. lemy.lol is blocked because of it’s fascist logo. That’s about it.
Fun fact 90% of piefed users can’t see your comment because the code comes with baked in blocking of hexbear and Lemmygrad lmao. If they can’t handle down votes they could never handle getting dunked on by us.
90% of Piefed users don’t federate with hexbear, but that’s because 90% of the Piefed instances are managed by teams who do not federate with hexbear on their Lemmy instances as well
List of Piefed instances that currently defederate hexbear:
https://feddit.online/, the same way https://fedia.io/ does (by the way, Fedia isn’t a software, it’s called Mbin, and doesn’t have such code, so not sure why you’re including them into your title)
https://quokk.au/, it used to be the same when it was still a Lemmy instance
As you can see, instances defederating hexbear are instances managed by teams which were going to do so anyway, as they already did on Lemmy. I’m still waiting for an example of an instance that defederated hexbear “by mistake”.
Instances who want to federate know how to do so, as we’ve seen above.
Setting up an instance isn’t trivial, assuming that admins would revise the defederation list doesn’t seem realistic.
Recent comment from an admin
This is exactly how it works. I started a PieFed instance and made the decision (during setup) to trim the defederation list down to none. Users can block on the account level.
I’m on my computer now, so I’ll type out some more detail if you’re interested. To reiterate, I’m just going off memory and it was two weeks ago so I could very well be making stuff up…
The pre-filled input box asked for each blocked instance to go on a new line, so:
To whichever admin deleted @Nakoichi’s comment for “disinformation”:
https://lemmy.world/post/32644237/18121152
https://codeberg.org/rimu/pyfedi/src/branch/main/app/cli.py
The removed comment for context
90% of Piefed users don’t federate with hexbear, but that’s because 90% of the Piefed instances are managed by teams who do not federate with hexbear on their Lemmy instances as well
List of Piefed instances that currently defederate hexbear:
https://piefed.fediverse.observer/list
As you can see, instances defederating hexbear are instances managed by teams which were going to do so anyway, as they already did on Lemmy. I’m still waiting for an example of an instance that defederated hexbear “by mistake”.
Instances who want to federate know how to do so, as we’ve seen above.
Setting up an instance isn’t trivial, assuming that admins would revise the defederation list doesn’t seem realistic.
Recent comment from an admin
https://wetshav.ing/comment/92409
More details from the same admin
lemmy.world lemmy.ml lemmygrad.ml hexbear.net lemmy.zip piefed.social etc...There are still a few instances that federate with hexbear, showing that the ‘baked in block’ is just a configuration change:
The removal reason:
It has been restored?
https://hexbear.net/comment/6446073
Yeah it got reversed a couple minutes after my comment