What if a browser could navigate #ATProto DIDs and 🦋 Bluesky handles? Made a little prototype of Aura, a browser that can navigate between standard websites (🌐), Bluesky handles (@), and permanent DIDs, resolving them all in the same address bar.
Sep 1, 2025 at 7:57 PM
README
This is a browser extension that provides “wormhole” navigation between different AT Protocol/Bluesky services inspired by Dame’s Shortcut. The extension transforms URLs and identifiers from one service to equivalent URLs on other services.
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.
Paul Klein IV on Twitter / X
I spent all of Christmas reverse engineering Claude Chrome so it would work with remote browsers. Here's how Anthropic taught Claude how to browse the web (1/7) pic.twitter.com/kBJA1DUWxA— Paul Klein IV (@pk_iv) December 29, 2025
handles.net | Bluesky Handle Management
Create and manage Bluesky Handles at your domain without configuring DNS for every handle.
SkyLink - Bluesky DID Detector - Chrome Web Store
Detects Bluesky DIDs in domain TXT records and .well-known/atproto-did files, linking to the associated profile.
New Custom Handlers component for Chrome – make everything intensely
The HTML Standard section on Custom Handlers describes the procedure to register custom protocol handlers for URLs with specific schemes. When a URL is followed, the protocol dictates which part of the system handles it by consulting registries. In some cases, handlers may fall to the OS level and and launch a desktop application (eg. mailto:// may launch a native application) or, the browser may redirect the request to a different HTTP(S) URL (eg. mailto:// can go to gmail).
Stop Ignoring the Browser: The Biggest Frontend Shift in a Decade
Native browser APIs now provide powerful alternatives for routing, state management, and components. Never mind the frameworks, use the browser.
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://...")
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
Important piece of multi-protocol support in browsers! Thanks to much work from Javi, and funding from @ipfs.tech. HEY NOW, settle down - a ways to go: - can only redirect to URLs/paths - no Safari - off by default in Chrome (for now) - only allow-listed schemes unprefixed Step by step...
Javier Fernandez
Blog post about a new Chromium feature I've been working on to allow Web Extensions register protocol handlers just declaring them in the Manifest. blogs.igalia.com/jfernandez/2026/03/24/protoco…
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 ✨
𝕮
A web extension that colors any link you've saved on @semble.so orange.
I've been pondering about having the browser resolve at:// URLs. I have been thinking that we could introduce a DNS-like (maybe DNS itself?) entity that goes from did:plc to URLs, the same way DNS goes from names to IP, and have the browser depend on that similar to how it depends on a DNS server.
The conversation in this 🧵 between @anna.germnetwork.com, @sgo.to, + @bnewbold.net has me hopping in my chair with excitement Can we finally implement the full potential of the @-ness of handles vs. sites?
bryan newbold
my response to anna's original idea is that handles are already domains, and there should be cool sites there. eg, if you put dril.bsky.social in a browser bar today, you get redirected to bsky.app/profile/dril.bsky.social instead, dril.bsky.social could be a webpage, like linktree (blento is a link app)
