2 days ago
- at:// URIs place the user as the authority, not the hosting server, using handles that resolve to immutable DIDs.
- Resolving an at:// URI involves three steps: handle to identity (DID via DNS or HTTPS), identity to hosting (DID Document), and hosting to JSON (via getRecord endpoint).
- Handles can be changed without breaking links by using DIDs as canonical identifiers, forming permalinks.
- Two DID methods exist: did:web (tied to a domain) and did:plc (from a public ledger, more portable and resistant to domain loss).
- The DID Document contains the handle, public key, and service endpoint, enabling verification and data location.
- Practical resolution tools include SDKs, caches like QuickDID, and services like pdsls or Taproot.
- The AT protocol abstracts over HTTP, DNS, and JSON to give users ownership of their data independent of apps.