Finalizing our new Shortcuts system. In this example we're using @atmo.garden, a new integration. Not every AT Protocol service uses identifiers like c/, so users can now create their own shortcuts. For example, @semble.so could be s/, sem/, or even /👀. This allows fast and quick results 👀
Jun 4, 2026 at 4:45 AM
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.
i'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">
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
