Fedia and Piefed have baked in code to block their users from seeing our replies, posts, and comments, while allowing a form of one way federation.
I think this warrants a fediverse wide boycott of all piefed/fedia instances until this is rectified.
I have removed the piefed instances that did not unblock hexbear from our allow-list to prevent the one way federation
Awesome thank you.
"wow switching to piefed cured my Havana syndrome":
Isn't this how it's always worked? I think it's the same with lemmy.world where you can see comments from .world users on Lemmygrad but they can't see your replies.
You can still federate after the instance setup, like piefed.zip does
You said I spammed this, but you still didn't register the information?
I think it's more that the admins are the only ones that can do that.
See this comment: https://lemmy.ml/post/35276820/20723645
Long story short, instances who defederate hexbear were doing so on their Lemmy instances anyway
Omg dude we get it stop spamming this. We know. That is not what this is about.
If someone runs an instance that has manually unblocked us cool but that is not what this is about and you are clearly the one not registering what I am pointing out here
You are presenting this like the baked in code forces one-way federation, when it's clear that the admins can update this later.
Example of two Piefed instances that currently federate hexbear:
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.
Instances who want to federate know how to do so, there are three examples.
Where is that code? Does it block some specific instances or how does it work?
For hexbear + lemmygrad it's by default
from what I can tell, when a server is spun up there's the option to subscribe to an existing blocklist on a piefed server.
This means blocklists can propagate transitively:
If instance A blocks lemmy.ml, and instance B subscribes to A’s blocklist, and instance C subscribes to B’s blocklist, then whatever instance is blocked on A will also end up blocked on C (unless filtered out manually).
quoting the developer of piefed, hexbear and lemmygrad are blocked by default:
This is why piefed is so popular with centrist extremists.
Piefed just seems like it's going to be a social chauvanist echo chamber, most people like Lemmy because even though the devs have their own ideological principles, it doesn't pre-configure the user experience based on those principles.
Harcoded block lists in your software? Gross.
Bruv, OP asks 'What's your stance on Genocide?' and then refers to Ukraine and China rather than Israel, that's bad enough, but then the PieFed guy replies with that 'they ban speech which minimises atrocities committed by Hamas in Gaza'! Sheesh.
Thanks. That's unfortunate. But everyone running an instance will know about blocked instances sooner or later and can get them if the list of they like.
The blocklist subscription would be super useful on mastodon but I think the threadiverse is a bit different. However I'm on my single user instance and am subscribed to communities on other instances only, so I already get a pre-moderated experience even if I don't block any instances myself so far so is experience doesn't match that of the admin of an instance with more users and own communities.
I think it's annoying, but im not sure if there's a clear solution. Id say this type of one sided block is similar to ghost bans and feels just as abusive.
I cant imagine it's very pleasant on their side either, since it would feel as if everyone from grad or ml were giving you the cold shoulder and make the fediverse feel dead.
The nature of the fediverse is open though - escalating this to another ban/block or banning the custom fork would be counterproductive, imo. If thats their preferred way to curate content, I guess thats their prerogative
Can you point to the file in the pieced codeberg repo that hardcodes these blocks?
I need to understand if this is a block built into the software, or just an option the operators who deploy piefed have set in a blocklist.
It's a default option: https://codeberg.org/rimu/pyfedi/src/commit/f3e863d277932b55a15b1fe5043d750994fb8c14/app/cli.py#L116
Admins can obviously edit it later on, like those instances do:
@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.
I'd argue it's more of an issue for them, since they do not get to counter-argument :P
Your reply refuting their argument can be read by everyone that is in an open platform, while their messages only go unchallenged on their own echo chamber anyway.
To me, it would be worse if it was the other way around: them spewing shit and me not even realizing and being unable to respond.
In my experience, fallacious arguments spill and unravel over several comments, rarely up front, so it's not a great thing.
Funny side note: hexbear blocked one of my diet communities at the instance level, so the echo chamber goes both ways.
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?
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?