> A community proposal for mapping web pages back to AT URIs.
Declare and resolve website links for at:// URIs. A demo of the me.byjp.atproto.deeplink lexicons.
Aturi is evolving! We’re now a browser extension for Fast Traveling around the Atmosphere: • Auto-redirect to favorite clients • Quickly switch apps • Copy universal links Automatically open @bsky.app links in clients like @anisota.net, @blackskyweb.xyz, @reddwarf.app, & more! Download: aturi.to
Aturi is evolving! We’re now a browser extension for Fast Traveling around the Atmosphere: • Auto-redirect to favorite clients • Quickly switch apps • Copy universal links Automatically open @bsky.app links in clients like @anisota.net, @blackskyweb.xyz, @reddwarf.app, & more! Download: aturi.to
Aturi is a new service that provides universal links for traversing/sharing content in the ATmosphere. Share @bsky.app posts or @atproto.com data with in a way that lets recipients choose where they want to view it — @blackskyweb.xyz, @leaflet.pub, @anisota.net, @pdsls.dev, and more! aturi.to
aturi.to - Universal links for the ATmosphere
aturi.to
Anisota
ATmosphere Waypoints Powered by a new sister service called @aturi.to, navigate to different areas of the ATmosphere automatically like @blackskyweb.xyz, @leaflet.pub, and more. ➳ Jump to clients or apps ➳ Copy links to specific waypoints ➳ Configure default waypoint behavior anisota.net
What are you’re thoughts on making this breaking change more inclusive to any AT URI? Like for @semble.so it would be very useful to have this mapping or any webpage that has a corresponding AT record (e.g. microblogging, standard.site, steamplace videos）
If you're an #atprotodev I'd love your thoughts on this short proposal. I think we'd all benefit from a way to tag our HTML to reference the at:// uris they're derived from! @popfeed.social, @bookhive.buzz, @sifa.id, @leaflet.pub, @pckt.blog, @offprint.app and many more — penny for your thoughts?
Atproto markup for HTML
byjp.leaflet.pubthis is also a thing, but separate from the basic website stuff anna is talking about. the at:// potential is sort of about navigating to that sort of URI in browser bar. but I think more realistically, having anchor links. <a atref="at://..."> (or more realistically: data-atp="at://...")
I think this breaking change for standard.site needs to become an ecosystem-wide conversation and convention. Any web page that represents a corresponding AT record needs to include a meta tag that includes that record. <meta name=“at:uri” content=“at://…” \>
rich harris
atproto/@standard.site friends: any thoughts on this issue? This... <link rel="site.standard.publication" href="at://..."> ...is invalid HTML, per html.spec.whatwg.org/multipage/semantics.html#the-…, because DIDs aren't hostnames. This causes problems with some tools. Issue here: github.com/sveltejs/kit/issues/15935
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">
