LightNews LightNews
fliegendestiefaffe.bsky.social
@fliegendestiefaffe.bsky.social
120 followers 77 following 1 posts
Posts Replies Media Videos
Reposted
countrydaddies.bsky.social
November 28, 2024 at 4:16 AM
Reposted
countrydaddies.bsky.social
November 29, 2024 at 1:08 AM
Reposted
dancow.bsky.social
No one said decentralization — which allows users to control their own data — would be easy

github.com/bluesky-soci...
Github issue: Ability to remove a follower Response by pfrazee: This is something we've discussed pretty heavily internally -- we don't yet know how to do it reliably. The issue is that every user controls their own dataset. When I "follow" somebody, what I'm doing is publishing a follow record on my account. When I block somebody, same thing: I publish a block record. A block record can override the behaviors of a follow record, but it can't force-remove the follow record from somebody else's repository. We have discussed a voluntary removal of the follow record. That is, if somebody blocks me, my server automatically deletes my follow record. The only concern is that it's impossible to force. A server that's misbehaving (intentionally or not) wouldn't delete the follow record, so there would be some confusing scenarios where soft-blocks don't work. That led to some discussion of whether we could try to enforce voluntary behaviors by social pressure (eg "Follow the protocol or your server will be penalized") but we haven't established a framework for that kind of governance yet so we're hesitant to move forward with it. A subsequent proposal to require "follow requests" has been discussed (bluesky-social/atproto#1352) which is technically feasible but adds a little more friction than we want for the default model. That leaves us where we currently are, which is tracking these two options but not ready to move on either yet.
November 20, 2024 at 4:15 PM