Gregory's ServerUsers, clearly, think a lot more of Bluesky is decentralized than it is, and realize less of the consequences than they should. This really worries me. Blocks and DMs are both great examples of this.
|
385 comments
 @cwebber@social.coop https://clearsky.app/ is creepy as shit lol and it shows just how much is public  It is ONE thing to be able to block JK Rowling and for you to see that JK Rowling is blocking you. It is an ENTIRELY DIFFERENT THING for ANYONE to see who is blocking JK Rowling and who JK Rowling is blocking This one is shocking to me: this seems like a vector for abusive actors  @cwebber@social.coop Already happening, bots scrape and harass people who sub to a labeller marking transphobes or something Now to be completely fair this is something that Bluesky's devs are interested in potentially changing: there is an open issue to discuss the possibility of private blocks https://github.com/bluesky-social/atproto/discussions/1131 What I am saying is there are architectural consequences to fundamental design abstractions Yes, I may sometimes seem silly over here, SICP-hugging fangirl, come on we're just trying to build things that *work* over here Look I'm a lisp lady, I know the realities of "Worse Is Better" more than most, I now the right CS designs don't win But Conway's Law flows in two directions! You know what, we'll come back to "bidirectional Conway's Law", let's talk about Direct Messages for a minute because I think those are telling Direct Messages in Bluesky, wait how do they work if ATProto is public? Did you guess? DMs are centralized! All DMs flow through Bluesky Now to be completely fair Bluesky is clear about this *in their blogpost announcing DMs*, but just like this thread, I doubt nearly anyone has read that far (am I talking to the void? I don't know, if you actually have gotten to this message reply with "I found the easter egg" or something)     @cwebber i found the easter egg! (Actually readin this thread in semi-realtime)   @cwebber@social.coop i mean you're on my timeline every 2 seconds, it's hard to miss The thing that is telling to me about DMs is that we *have* federated direct message protocols like XMPP which have been around for ages; if Bluesky wanted to they could have tacked that on pretty quickly, E2EE or not. It still would have been decentralized at least The point is that I have *seen in the wild* people saying "Oh yeah Bluesky added DMs to their decentralized protocol" and augh I know they aren't claiming this but it's very clear to me that people are reading things as being completely different architecture than it is But to Bluesky's credit, Twitter's DMs aren't decentralized either! And getting and shipping something that works, now for the influx of Twitter users, again... I am sympathetic Bluesky's team is doing an INCREDIBLE JOB in that way of scaling to meet the incoming stream of Twitter refugees On that note, again, I am not reading the replies right now because I am (a) afraid to and (b) I'm never gonna finish this and we are a bit over HALFWAY THROUGH the analysis but I have this fear that EVERYONE is mad at me, Bluesky fans, fediverse fans I am trying to be analytical. I am trying!!! I said we are about halfway through and criminy we're halfway through the afternoon, I need a break to get some tea We have a few big topics left: - Decentralized identity, how does it work (magnets too, yes) And so, it is TEA TIME Go get yourself a hot beverage. Put honey or agave in it, if you like. Dairy, or perhaps, non-dairy, if you prefer. === BREAK TIME! Time for tea! === I can confirm, @cwebber is currently making us both tea :)   @cwebber this entire thread is enlightening so far! (and i figure liking each post manually would be kind of insane to do.)  @cwebber indeed the `void*` is listening. Please do continue.    @cwebber I found your Easter egg. Please publish a count of all responses to this Easter egg. ๐  @cwebber yeah, I haven't been on Twitter in a hot minute but I lived there for years and you could see things like follows and the most telling was Likes, even before they started getting put in people's TLs, you could look it up -- which were legit the first way we found out JKR was a terf, she wasn't posting it yet or RTing even but she was constantly liking terf shit. However that was the most detailed info you could get on someone, the one thing they didn't necessarily intend to share. @cwebber oh my god yeah. some friends of mine were discussing this briefly yesterday; it seems like ripe fields for harassment and public shaming  @cwebber honestly kind of shocking that it's not fully encrypted, but then I suppose they would have to solve key management in a decentralized network problem ... Who cares if you block anyone ? They can still get the data , blocking is for fun I guess? |
Blocking first. Bluesky's decision to have *everything* public means that it is expected that every participating node knows *everything* about who's blocking *everyone*.
"This is consistent with how blocking works on Twitter/X" their paper says
But wait, I'm pretty sure that one's not true though