The AT-URI Syntax Mess - at:// pizza thoughts
Why AT URIs are not valid under IETF RFC-3986, what the impact is, and some possible ways forward.
README
This is a browser extension that provides “wormhole” navigation between different AT Protocol/Bluesky services inspired by Dame’s Shortcut. The extension transforms URLs and identifiers from one service to equivalent URLs on other services.
OAuth Patterns - AT Protocol Docs - AT Protocol
Auth for AT Protocol application developers.
OAuth Patterns - AT Protocol Docs - AT Protocol
Auth for AT Protocol application developers.
My take on "The AT-URI Syntax Mess": the canonical form should be percent-encoded, and today's colon syntax should stay as a defined lax input form. Longer writeup in the forum: discourse.atprotocol.community/t/the-at-uri-syntax-mess/934/…
The AT-URI Syntax Mess
discourse.atprotocol.community
bryan newbold
A /now lexicon for AT Protocol is taking shape. @tynanpurdy.com is defining `now.nownownownow.entry` -- simple records for sharing current-status updates, connected to Derek Sivers' nownownow.com ecosystem. Seeking a co-lead and schema feedback. Join the WG on Discourse.
Nownownownow.now a lexicon for /now
discourse.atmosphere.communityi'm seeing an unfortunate trend of atmosphere apps abandoning/forgetting the convention of including key protocol identifiers or URI components in their URL paths (rkey, handle, etc), making it impossible to easily locate/lookup the underlying protocol record makes adding @aturi.to support hard
Hey #atprotodev; should we make a convention for annotating HTML elements with the AT uris they’re built with? (So that, say, a browser extension could offer links to @pds.ls) Something like this? <li typeof="schema:Thing" resource="at://did:web:example.com/org.example.lexicon/rkey">
