It took me a couple of years to figure this out. The core reason why #nostr is going to win as a protocol: By creating a unique event id that is the digest of its: - author (pubkey), - meaning (kind), - timestamp (created_at), - metadata (tags), - message (content), and: signing of this resulting event id (sig) That means you can sign whatever the hell you want with whatever meaning you intend, and it can be uniquely stored or relayed anywhere. #nostr become the sword of simplicity that cuts through the Gordian Knot of interoperability bullshit and semantic capture. This simple format allows anyone to define whatever they want, with only a simple rule for cryptographic validation that it was actually they who created the event. With a few additional conventions it becomes a baseline protocol for social media, but can be expanded to an infinity of possibilities. Thanks for this genius, @fiatjaf image

Replies (9)

SoapMiner's avatar
SoapMiner 3 weeks ago
Elon tries to convince you that Xitter will be the everything app. Nope Nostr will be the everything protocol
I understood that pretty quickly. The other side of that is digital immutability. The consequences of that are understated and not well understood, and actively occulted, which pisses me off.
earthcuddle's avatar
earthcuddle 3 weeks ago
beautifully said: "the sword of simplicity cutting through the gordian knot of interoperability bullshit and semantic capture"
Default avatar
Duvel 3 weeks ago
Thank you for this explanation!
The closest alternative is DIDComm. Here are the reasons it can’t supplant #nostr 1. The “id” property is arbitrarily generated (not a digest) 2. The “type” is too complicated (kind is simpler) 3. The message does not have an identity associated with it (pubkey) 4. Assumes a messaging paradigm (to, from) versus a more generic publishing paradigm. 5. No singnature (sig) defined as part of the core message (event) image