We’re launching Lyria 3.5 in Google Flow Music, with advances across musicality, lyrics, vocals, and creative control
deepmind.google·6d ago
AI Engineering
Lobsters·Jun 29·5 min read
The AT-URI Syntax Mess
TL;DR
The AT URI syntax currently conflicts with established URI standards, causing issues in its implementation. The AT protocol uses Decentralized Identifiers (DIDs) in a way that disrupts the expected URI structure.
✦ Why It Matters
Engineers can better understand the implications of URI standards on decentralized identity systems.
Key Takeaways
- Review the current AT URI implementation for compliance with URI standards.
- Engage with the ATP Working Group for updates on standardization efforts.
- Prepare for potential disruptions in using AT URIs in applications.
- Explore alternative URI structures that align with existing standards.
Full Summary
AT URIs, part of the atproto specifications, are designed to empower individual accounts by placing Decentralized Identifiers (DIDs) in the URI authority section. However, this design conflicts with the hierarchical structure defined in RFC 3986, which governs valid URI formats.
The problem was first identified in 2025 and has gained urgency as more developers attempt to use AT URIs in contexts that require standard-compliant URIs, such as HTML link tags. The ATP Working Group at the IETF is now tasked with standardizing the AT URI scheme, which necessitates a permanent registration.
While the core concept of AT URIs—allowing accounts to be the ultimate authority for their content—remains intact, resolving the syntax issue is essential for broader adoption. Unfortunately, any proposed solutions will likely involve significant disruption for developers.
A concrete example of an AT URI includes a specific record with a DID in the authority position.