> One thing that I think this discussion is highlighting to me is that there's very little support in the web standard (as implemented by browsers) for surfacin

> One thing that I think this discussion is highlighting to me is that there's very little support in the web standard (as implemented by browsers) for surfacing resources to users that aren't displayable by the browser. Really wish registerProtocolHandler were more popular. And I really wish registerContentType hadn't been dropped! Web technology could be such a nexus of connectivity. We could have the web interacting with so much, offering tools for so much. Alas, support has largely gotten worse decade by decade. And few have taken up the chance. Bluesky is largely using at:// urls. Eventually we probably could argue for support for our protocol. But web+at:// is permission less. Tools like https://pdsls.com https://pdsls.com can just become web based tools, with near no effort, if they want.