22
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 18 Nov 2024
22 points (100.0% liked)
TechTakes
1441 readers
49 users here now
Big brain tech dude got yet another clueless take over at HackerNews etc? Here's the place to vent. Orange site, VC foolishness, all welcome.
This is not debate club. Unless it’s amusing debate.
For actually-good tech, you want our NotAwfulTech community
founded 1 year ago
MODERATORS
Interesting post and corresponding mastodon thread on the non-decentralised-ness of bluesky by cwebber.
https://dustycloud.org/blog/how-decentralized-is-bluesky/
https://social.coop/@cwebber/113527462572885698
The author is keen about this particular “vision statement”:
The assumption being, stuff gets enshittified and how might you guard your product against the future stupid and awful whims of management and investors?
Of course, they don’t consider that it cuts both ways, and Jack Dorsey’s personal grumbles about Twitter. The risk from his point of view was the company he founded doing evil unthinkable things like, uh, banning nazis. He’s keen for that sort of thing to never happen again on his platforms.
@rook @techtakes Dorsey is off the board now, as of this month I think.
I read that posts on BlueSky are permanently stored in a blockchain, which, if true, would put me off.
I’m aware he isn’t there now, but it bears remembering that he was there at the beginning when these goals were being shaped, and as we have seen with twitter there’s nothing to stop him coming back, even if nostr is his new best friend for now.
So, this is complex and hard to find concrete information on, but:
From bluesky’s own (non technical) blurb on the subject,
The merkle trees are per-user, which makes history-modifying operations like rebasing practical… this facility apparently landed last summer, eg. Intention to remove repository history. Flagging tree nodes as deleted, and then actually destroying them in a series of later operations (rebase, then garbage collection) would explain the front end respecting deletions but lower-level protocols showing older state for a little while.