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.

Which logo would you put in front of your ATprotocol handle if you had to put it on a poster or website? Mostly I've seen people using the Bluesky logo, but now there's mu.social, @eurosky.social, @blackskyweb.xyz and others, all with their own logo's, it's starting to get confusing.

Is there a reason why we only allow one handle to one DID? I get it as a product decision for bluesky itself, but I don't get it in the context of atproto as an ecosystem. what if I want to be `@taurean.bryant.land` here and `@taurean.work` on a professional service?

Internationalisation of "handles" on the fediverse, fresh from #fediforum lists.w3.org/Archives/Public/public-swicg/… @technical-discussion @hongminhee

Continuing down the path toward a fully independent phone... what about the actual phone part? 🎬 calling an atproto handle

for other atproto ecosystem folks: most things are working smoothly, but you may be seeing slow (high p99) handle resolution (via HTTPS well-known) for *.bsky.social handles (even projects which don't rely on bsky services often need to resolve handles as part of interop)

Is there a reason why we only allow one handle to one DID? I get it as a product decision for bluesky itself, but I don't get it in the context of atproto as an ecosystem. what if I want to be `@taurean.bryant.land` here and `@taurean.work` on a professional service?

open discussion on the intersection of @atproto.com and @iroh.computer