I needed to step away for a week because this comment section was giving me anxiety.
I know we both agreed the system is not perfect.
I haven’t come up with a solution
and you refuse to acknowledge that treating OP like dog shit isn’t an appropriate reaction for a non-technical user complaining about the confusion behaviour of a poorly named feature.\
I came into this conversation because people kept mocking OP. I’ve been pulled off on tangents fighting about stupid shit because I can’t keep my eye on the ball worth shit, but that’s basically it. People are dragging OP for daring point out that the way “block” works here is confusing and feels bad to use.
Even if it cannot be implemented, it is not unreasonable for a user to request it.
I also absolutely refuse to acknowledge that blocking is antithetical to decentralized systems. Just because it’s not possible with the current design of activity pub doesn’t mean that it’s not possible in other decentralized systems. I’m not looking for perfection, I’m looking for improvement.
Here:
In mastodon, if Alice from instance A follows Bob from instance B, then instance B will send Bob’s posts to A. In addition to that, when B sends Bob’s posts to A, it can also send new block requests.
These block requests are public, and it is up to the subscribing instance to honor them, but it’s most of the way there, and instance admins can choose to defederate with instances that don’t honor it (like they already do with malicious instances).
Lemmy isn’t mastodon, but it still uses activitypub, so decentralization isn’t the limiting factor here.
With Lemmy it’s actually more enforceable, since content in a community is owned by the instance hosting that community. If Charlie is on instance C, and tries to reply to Bob’s post on instance A, instance A could have subscribed to Bob’s blocklist, and will reject Charlie’s reply because it’s in reply to Bob’s post. On Lemmy it doesn’t even matter if Charlie’s instance is malicious or not, as long as A isn’t.
Malicious is the wrong word, but I think you get the idea.
I needed to step away for a week because this comment section was giving me anxiety.
I know we both agreed the system is not perfect.
I haven’t come up with a solution
and you refuse to acknowledge that treating OP like dog shit isn’t an appropriate reaction for a non-technical user complaining about the confusion behaviour of a poorly named feature.\
I came into this conversation because people kept mocking OP. I’ve been pulled off on tangents fighting about stupid shit because I can’t keep my eye on the ball worth shit, but that’s basically it. People are dragging OP for daring point out that the way “block” works here is confusing and feels bad to use.
Even if it cannot be implemented, it is not unreasonable for a user to request it.
I also absolutely refuse to acknowledge that blocking is antithetical to decentralized systems. Just because it’s not possible with the current design of activity pub doesn’t mean that it’s not possible in other decentralized systems. I’m not looking for perfection, I’m looking for improvement.
Here:
In mastodon, if Alice from instance A follows Bob from instance B, then instance B will send Bob’s posts to A. In addition to that, when B sends Bob’s posts to A, it can also send new block requests.
These block requests are public, and it is up to the subscribing instance to honor them, but it’s most of the way there, and instance admins can choose to defederate with instances that don’t honor it (like they already do with malicious instances).
Lemmy isn’t mastodon, but it still uses activitypub, so decentralization isn’t the limiting factor here.
With Lemmy it’s actually more enforceable, since content in a community is owned by the instance hosting that community. If Charlie is on instance C, and tries to reply to Bob’s post on instance A, instance A could have subscribed to Bob’s blocklist, and will reject Charlie’s reply because it’s in reply to Bob’s post. On Lemmy it doesn’t even matter if Charlie’s instance is malicious or not, as long as A isn’t.
Malicious is the wrong word, but I think you get the idea.