It’s technically interesting, but if there’s already a dependency on DNS, why introduce an additional dependency on DIDs? Not sure how that comports with stated design goals for the protocol, and just repeats patterns from more well-established decentralized protocols. t.co/R0UR0tfGW6
Conversation
Replying to
The repo & Lexicon schematic are pretty good (as @jackyalcine notes, they obviously learn a lot from the many prior attempts at this work) and it’s not overly plagued by “web3” bullshit. But the “algorithmic choice” part feels like wankery that’s mostly there to appease Jack.
1
7
Of course, this is a bit like trying to rate a restaurant by reading its recipes; if anyone has actually dug into in more depth, please do share your experiences!
1
4
More good context, though if Musk-era Twitter adopts an open protocol because they think it’s some kind of dunk on having responsible content moderation, it’ll be a fitting end to Twitter’s years of cultural relevance.
Quote Tweet
Hey @JosephJacks_ the Bluesky org is a public benefit corp led by @arcalinea. @dholms_ & @pfrazee work for @arcalinea.
I think there’s some #UCAN usage in the stack and lots of DIDs — open community standards that many of us collaborate on. twitter.com/JosephJacks_/s…
1
1
14
If you read any coverage of Bluesky/the AT protocol that ignores the literal decades of prior work in this space, or that attributes it to being a project by Jack (I’m sure Parag had far more input), you can ignore it as incompetent fan fiction, not a fact-based analysis.
1
1
13
Replying to
I think it allows someone to move to a different service. If the user doesn't control the domain name they use a DID that doesn't depend on it. The last section of doc 👇shows the difference between someone who owns their domain and someone who doesn't:
