there’s a fun drinking game you can play where you take a shot whenever the spec devolves into flowery nonsense
§1. Purpose and Scope
The purpose of DIDComm Messaging is to provide a secure, private communication methodology built atop the decentralized design of DIDs.
It is the second half of this sentence, not the first, that makes DIDComm interesting. “Methodology” implies more than just a mechanism for individual messages, or even for a sequence of them. DIDComm Messaging defines how messages compose into the larger primitive of application-level protocols and workflows, while seamlessly retaining trust. “Built atop … DIDs” emphasizes DIDComm’s connection to the larger decentralized identity movement, with its many attendent virtues.
you shouldn’t have pregamed
You must log in or register to comment.
some context for those less cursed than me:
DID is one of the foundational technologies behind bluesky. it’s also web3 nonsense, and bluesky’s implementation of it is a no-op. see this mastodon thread for more details on how bad DID is
DID is a W3C spec (one of the worst ones), but DIDcomm is closer to a cryptocurrency whitepaper in how nonsensical it is. this isn’t a coincidence, the authors are all crypto folks