<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Regarding the validity of at:&#x2F;&#x2F; URIs in atproto:]]></title><description><![CDATA[<p>Regarding the validity of <code>at://</code> URIs in atproto:</p><p><a href="https://bnewbold.leaflet.pub/3mph4hzvbdc2v" rel="noopener">https://bnewbold.leaflet.pub/3mph4hzvbdc2v</a></p><p>We have a similar problem with <a href="https://fediverse.codeberg.page/fep/fep/ef61/" rel="noopener">FEP-ef61</a> 'ap' URIs. In their canonical form, they are not valid RFC-3986 URIs.</p><p>I think if atproto devs decide to move away from <code>://did:..</code> syntax, we'll have to do that as well.</p><p><a href="https://mitra.social/collections/tags/fep_ef61" rel="tag noopener">#fep_ef61</a></p>]]></description><link>https://fedi.wiki/topic/a9782657-1aa9-4768-9b16-6f8a0f7b3631/regarding-the-validity-of-at-uris-in-atproto</link><generator>RSS for Node</generator><lastBuildDate>Sun, 26 Jul 2026 02:08:53 GMT</lastBuildDate><atom:link href="https://fedi.wiki/topic/a9782657-1aa9-4768-9b16-6f8a0f7b3631.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 29 Jun 2026 19:45:16 GMT</pubDate><ttl>60</ttl></channel></rss>