I have removed the piefed instances that did not unblock hexbear from our allow-list to prevent the one way federation
this post was submitted on 27 Aug 2025
49 points (96.2% liked)
Fediverse
21449 readers
9 users here now
A community dedicated to fediverse news and discussion.
Fediverse is a portmanteau of "federation" and "universe".
Getting started on Fediverse;
- What is the fediverse?
- Fediverse Platforms
- How to run your own community
founded 5 years ago
MODERATORS
@dessalines@lemmy.ml @davel@lemmy.ml I am curious as to your thoughts on this. It is very annoying for myself and others to write out effort posts refuting shit these liberals spew on our platforms only to find out none of them will ever see it. Meanwhile we have to be subject to their garbage posts and takes with no recourse. This is fundamentally detrimental to the fediverse as a whole.
There's nothing we can do about server-to-server blocking, but I think over the long term, people will join servers that do less instance blocking, so that they can personally be in control of what they see.
And of course everyone not on restricted servers will still see your replies / takedowns, so it really only harms them. In a big way, responses are just as important to onlookers, than the one you're responding to.
Pardon my ignorance of how federation works, but would it be possible to have federating/defederating at a more granular level, like at the user or comm level? Like if in individual user wanted to block a whole instance instead of instances blocking each other, or if instances wanted to prevent certain comms from showing up and not others for a specific instance?
That's the way we'd prefer it, and it's already working in lemmy. But unfortunately that wasn't added until after full instance blocking, so most instances kept their blocklists.
We have instance community blocks working rn, and instance user blocks will be in the next release.
Of course I do think instances should fully block some servers, like the ultra right kiwi-farms and stormfront type ones... but unfortunately those communities set up on the big instances now anyway.
That’s really great to hear and it seems like it will be a very positive change. Thanks for the response!
Oh yeah for sure I was just curious as to your thoughts on people taking this project and building in their own ideologically motivated blocking. I know that there is nothing to be done about it as its all open source I just find it scummy that they do this in the first place. I get not wanting to federate with specific instances but the way this works is to just automatically make it one way only unless the person using their fork manually changes it.
I don't want to force them to see our posts or comments or anything idgaf about that I just don't want to have to guess which people I can see on my end can actually see my replies to them ya know?
unless the person using their fork manually changes it.
Updating the defederation blocklist is done via the admin UI. A fork implies having to recreate the source code and modify it. This is different.
Recent comment from another 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.
Whatever, point still stands it's shady AF and you are obsessed with defending it and I really don't give a shit how you spin it.
load more comments
(5 replies)
"wow switching to piefed cured my Havana syndrome":
view more: next ›