Declare and resolve website links for at:// URIs. A demo of the me.byjp.atproto.deeplink lexicons.
Protocol Handler Registration via Browser Extensions – make everything intensely
Custom URL schemes have traditionally served as an integration bridge between the browser and external capabilities. Schemes such as mailto: and tel: allow navigation to trigger actions beyond ordinary HTTP resource retrieval. The HTML Standard formalizes this mechanism through the Custom Scheme Handlers API, which enables websites to register themselves as handlers for specific URL schemes.
Web Tiles
Trust has been the defining constraint on the Web's evolution towards more powerful, more applicative capabilities. In a Web context, the user must be able to safely load any arbitrary URL, to safely click on any arbitrary link. The way in which this is achieved is that the runtime places strict limits on what a Web page can do, which in turn necessarily limits powerful capabilities. Could we get more power using a primitive that places more stringent constraints in what pages can do?
Web Tiles
Trust has been the defining constraint on the Web's evolution towards more powerful, more applicative capabilities. In a Web context, the user must be able to safely load any arbitrary URL, to safely click on any arbitrary link. The way in which this is achieved is that the runtime places strict limits on what a Web page can do, which in turn necessarily limits powerful capabilities. Could we get more power using a primitive that places more stringent constraints in what pages can do?
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">
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）
I wonder if atmospheric websites (websites were most or all of their content is natively stored on the AT protocol) would alleviate this because there are so many places to get the content that aren’t just the website
Kuba Suder 🇵🇱🇺🇦
If you run a blog, website, other publicly readable web thing: do you have any kind of noticeable LLM scraper bots problem (i.e. ongoing huge number of bot requests that you have to fight with)? If you do, what is it that you run and that they're requesting (and how are you defending)?
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://...")
Could we share theme data under AT protocol? I think we can! blog.damato.design/posts/theming-atproto/ (oh, and hey my standard.site integration works!)
Theming atproto
blog.damato.designIs 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.
@standard.site profile record, used to build a Linktree™-type web page for every author 🤔 Is this anything?
