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">

Seriously mild take: ATProto web clients should serve a <link rel="alternate"> containing an at:// URI I've just opened a PR to do this on Frontpage and atproto-browser. I'd for other clients to follow along with the convention! github.com/likeandscribe/frontpage/pull/…

Wanted to take a peek at @semble.so and didn't knew where to start. I built this as a static explorer of all the links in there. sites.wisp.place/davidgasquez.com/semble-links… Love AT Protocol for letting me build the UI I want! 😍

Wanted to take a peek at @semble.so and didn't knew where to start. I built this as a static explorer of all the links in there. sites.wisp.place/davidgasquez.com/semble-links… Love AT Protocol for letting me build the UI I want! 😍

this 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://...")

Is there interest in an ATProto service that given any URL, returns a unified backlink summary across the ecosystem? E.g., bookmarks on @semble.so , mentions on Bluesky or @standard.site , annotations in @margin.at, etc.

@atpi.at is live. A tiny set of tools and integrations to resolve AT Protocol URLs and preview atproto JSON data! - Direct URL prefixing (atpi.at//...) - npm pkg - Chrome Extension - VS Code Extension and... some fun ones! Check out: docs.atpi.at It’s not just an API. It’s ATPI. GET it?

Building on some of @chrisshank.com's work, what if we had browsers that were atproto-native? orange link = in your PDS green link = in the PDS of someone you follow Dreaming about the future of social hypertext ✨