Post

brian
@briancloutier.com

I always assumed PLC uses some kind of merkle-powered append-only ledger a la certificate transparency, call me a crypto bro but that's the right way to do what PLC attempts to do appalled to find out today PLC uses the nostr approach but with a single trusted relay which can censor anything 😮

0 reposts3 likes

Everett Bogue 🔵
@evbogue.com

I agree it's kind of silly that there's no did:ed25519 here. But Nostr suffers from having no merkle anything between the posts. And NIP-26 forces devs to index the entire network to say that (thiskey === thatkey) which is simply not a real thing in cryptography.

brian
@briancloutier.com

a raw public key did would be nice but plc & web serve the important purpose of letting you take a did and lookup the address of the user's pds, I see why they did it this way the part I'm objecting to is plc did docs are fully managed by a server they control w no protections against censorship

Everett Bogue 🔵
@evbogue.com

I agree with you. Once I read that the did:plc for each user is a substring of the hash of their first post but kindof got lost in the docs just now trying to see if it's still that way. Do you have a thesis about why did:plc records are stuck on the Bluesky server?

brian
@briancloutier.com

they've been rapidly shipping features to get feature parity with twitter, DMs are also implemented weirdly, I have to imagine matching twitter is their biggest priority right now and they plan on coming back to clean up later. Current PLC is the simplest future-compatible thing that works