The Piefed system of blocking is more aligned with how most other sites do blocking
I don’t know any other site that allows blocked users to reply to the blocking user but deletes the reply on the backend server for everyone on it.
But regardless - that decision was made unilaterally by piefed and corrupts the federation of the rest of the network. Huge holes of mis-matched comment threads are being created everywhere because piefed chose to implement a destructive blocking system rather than a front-end filter, or by working with the other implementations on a solution that doesn’t misalign data across the network.
I understand that you agree with how piefed restricts certain content - my point is that the way piefed has implemented those features corrupts the integrity of the entire network. They’ve made it clear that they have no interest in collaborating with the other developers, even if it means creating incompatibilities between the integrations to the point of functional defederation.
“Move fast and break stuff” isn’t something anyone should be aspiring to.
Skavau@piefed.social 2 days ago
It doesn’t. On Piefed if you are blocked, you should be unable to reply. It is whited out. But Lemmy obviously doesn’t work like that so incoming replies from users who are blocked, coming from Lemmy, just have it automatically thrown out.
Did Lemmy take a democratic vote about how they wanted blocking to be handled? Some users prefer someone they block being unable to reply to them. I have even seem this expressed on Hexbear.
anarchiddy@lemmy.dbzer0.com 2 days ago
Yes, that’s exactly what i’m pointing to. Rather than implementing this in a way that’s non-destructive and transparent, they’ve created an asymmetry by dropping comments entirely. They could render comments based on block-checks and not create this problem, but instead they chose to say ‘fuck the lemmy instances’ and create hundreds of holes in the federated activity out of seemingly nothing but spite.
Not “other developers” generally, “the other developers”. I’m speaking specifically of the already existing lemmy codebase. Piefed was created as an alternative to lemmy - at least in part - because of disagreements over the developer’s political views. It wasn’t because lemmy was poorly written, it was because a couple of developers decided they wanted to fork the project into their own that they could manage independently from lemmy.
Skavau@piefed.social 2 days ago
How could Piefed make this disparity of blocking philosophy mesh with Lemmys here? If Rimu thinks that a block is a block, and that users who are blocked should not be able to go on replying to the user who blocked them, then I don’t see why he would carry comments just because they come from Lemmy.
Correct. But even if there was no ideological dispute here (he also disliked the development cycle and choices - I don’t want to make too many assumptions here), rimu may still have made his own reddit clone or someone else may have - which would handle things very differently.
anarchiddy@lemmy.dbzer0.com 1 day ago
Without forcing every server to adopt the same blocking system universally? It can’t. What it’s doing now is functionally no different than if they hid replies on the user front end for users blocking others outside the home instance, except instead of doing this non-destructively (and preserving data pairety across instances), they’ve decided to blow huge holes in the federation service that are no longer mirrored on the other instances.
If the piefed method of handling blocking is to make it impossible for all users in every instance incapable of replying to a user who has blocked them, then every server would need to adopt the same method universally. Piefed has every right to hide content from their users that their users have chosen to block, but doing so by rejecting that content for the whole server while the rest of the network carries on ends up creating shadow forums on every instance.
That would be preferable to the ‘embrace, extend, extinguish’ path that they are currently on.