Oh and I also saw who blocked *ME* - that took about 3 seconds, the information is just a click away. (No hurt feelings there, but still, truly horrified this is public information - do the blockers know this?!?)

As @cwebber wrote: "[On Bluesky] everything is public, including who you block" https://dustycloud.org/blog/how-decentralized-is-bluesky/

@_elena As per the op the public nature is an inherent of the design and it is even up to an app to respect or not (so someone could write a block-ignoring app, like the one you pointed out).

Since blocking for any reason or none is part of the culture there (imho a great thing), one could perhaps camouflage any particular block with volume, say by using block lists.

Of course people can still look for specific blockers for abuse, but there's a good chance many others are also blocking them..

@_elena @cwebber Holy fuck!

In theory, the same is true for activitypub (it was not designed for avoiding abuse, because fucking neckbeards), but I am not aware that there is a way to easily collate usernames (because of all the different instances), so it's not so big a problem.

@_elena When I learned about this, I rushed to Bluesky to make a rare post and "warn people".

But first, I wanted to search if anybody's talking about this. And people seem to already know! And are fine with it?

I think folks are already hooked, and it's like telling everyone that Twitter/X is a nazi bar two years ago.

@_elena @cwebber

I would really proud to make my block list public.

@_elena Impressively bad implementation based on their reasoning. This is a solved problem on Mastodon. Guess it's a weakness to the AT Protocol since all those "data banks" need to communicate with the master server. Oops.

https://docs.bsky.app/blog/block-implementation

@_elena @cwebber

That's a black eye for Bluesky.

It's like publishing the names and addresses of crime victims.

"Unlike on other centralized platforms, blocks on Bluesky are public and enumerable data, because all servers across the network need to know that they exist in order to respect the user’s request."

https://docs.bsky.app/blog/block-implementation

@_elena @cwebber the safest choice is to not use Bluesky.

Trading one fascist run network for another is just asking for more of the same

@_elena @cwebber I'm not surprised. They seem to make a big deal about the openness of their data. It almost makes you wish they were selling it. At least the audience would be smaller.

But... What I have noticed is that if someone follows you and you block them, they disappear from the list of your followers, BUT your follower count doesn't decrease. I found that odd.

@_elena @cwebber
@mastodonmigration

Hmm...

Not already same capability for muting...??

If not, bet there soon will be.

Seems a thoroughly idiotic inclusion of an API feature that I'm betting isn't limited to "block".

@_elena @cwebber

I'm curious why anyone would even *want* to see someone's block list.

Like, that just seems very high school and *let me stir the pot*-ish.

@_elena @evan @cwebber Thanks for alerting everyone about this!

The only reason I do not publish my public block list on #Mastodon is that it requires extra time & energy typing in the explanation.

If someone sees my block list on #Bluesky, then it will not bother me, as I am barely on Bluesky at all.