What could possibly go wrong?

that isn’t the dumbest shit I’ve heard this week, but it’s pretty close. Why would they do that?

Right now, blocks won’t work with third party Bluesky clients because blocks are not currently supported in AT protocol.

It surprises me that this feature is still not available protocol-wide.

Jack’s a dick.

that is really, uhhmmm, how to put it politely? Stupid.

Making the act of blocking or muting someone public can result in retaliation & that person evading the block. *sigh*

I have heard people say I'd rather have a list of who has you blocked more than to know who your followers were. Dystopia social media. The enemy of my enemy is my friend?

yikes

I can see that being problem in that it gives the blockee an unintentional boost, but personally I want everyone to know who I blocked so they can block them too. I'm more of the school of:

That's a dealbreaker for me. Not that I was ever interested in going there, mind you.

That is utterly horrendous, not to mention horrific! Your blockist should be on a strictly need-to-know basis, which basically should be you (directly) and the service's (through indirections as necessary to maintain your privacy).

@rmondello isn't this kind of required to implement blocking? Servers need to know who I blocked to not show my boosted posts to blocked users in the federated timeline

this is the worst

It's... public? That's... so many levels of disturbing. There's so much harassment potential there. Damn.

🤔 And people wonder why I chose Mastodon...

This app has a lot of intentional "features"