Can confirm!

Something that feels off to me is that all TLDs are created for apps, not people.

I'm sgo.to, but I have no affiliation to tonga.

Thats why I think we need a fundamentally different TLD: one for people, not apps.

This is entirely driven by Microsoft!

Really good stuff!

Yeah, agreed that scarcity is a problem ...

... Maybe it is an existing problem that gets exacerbated? Meaning the scarcity already exists, right?

I'm Brazilian, so I always told my ex-girlfriends that when they become my ex's they'd become an ex-goto (which also translates to sweet in Portuguese) so they should avoid breaking up :)

Like this: bsky.app/profile/sgo....

I don't think we'd need to change anything in DNS/IANA.

This suggestion is based on how subdomains currently work.

i.e. if @germ is just syntactic sugar for germ.handle, than germ.handle can have an arbitrary number of sudomains, such as goto.germ,handle, which transpiles back to goto@germ.

No way!! @developer.chrome.com is here!!!

Who is running this account? Kinlan?

My posting to this site here will directly correlate with how close we are to the IRS tax deadline because I'll take every single opportunity to avoid, escape real life and procrastinate.

I'm sorry if I entirely disappear after the 15th.

I think this is more or less what we arrived at with subdomains here:

bsky.app/profile/did:...

Handles partitioned by app.

We could obviously use the notation anna@germ too, and I think that would work out for subdomains.

WIth @bmann.ca idea of subdomains, I think it would give you almost exactly what you have in your profile username: @anna.germ, because @germ could hand off a subdomain to you.

bsky.app/profile/sgo....

Something that might be interesting is that if we had a TLD, than we could have users in subdomains, e.g. @boris.sillygoose and @sillygoose (or anyone else) could hand out an arbitrary number of subdomains to anyone it wanted to.

If I had @goto, I could give @dani.goto, @sam.goto and so on ...

Good luck, wishing you the best here too!!

.me also occurred to me, but that's already taken

Yeah, for sure. It has to be "cute enough".

I'm thinking ICANN because it helps making things backwards compatible with browsers ... if it requires every browsers to redeploy before the system is useful I think it is DOA.

Yeah, .at I figured was already taken.

Any other names?

Do you buy my argument that the suffix isn't too important if browsers hide it as @user?

On routing, maybe rather than hitting the DNS TXT record, we just reuse the DNS CNAME records, so that goto.handle can redirect to whatever URL whoever controls the handle wants to (as @anna.germnetwork.com was saying, e.g. to a Sifa URL).

I think most people don't know what an "App Password" is :)

I've been working full time for the last decade or so on authentication mechanisms for the web and ran into this concept from this thread :)

This might be a similar discussion I was having with @anna.germnetwork.com here:

bsky.app/profile/anna...

It would take a while to have every browser support the @goto notation, but in the meantime, this would do:

<a href="https://goto.handle/photos/me.png">

Which browsers that *do* understand the .handle TLD could be smarter about.

So, when you go into a browser, and type @goto into the URL bar, it queries the DNS TXT _atproto record to figure out where your PDS is at and renders it as a website.

If a user copy/pastes @goto, it pastes as goto.handle so that it works with systems that don't know how to parse @goto.

We can also bikeshed what the TLD suffix is (.handle?, .at?, .atproto?, .username?) but I think that's roughly unimportant because I'm hoping we would be able to introduce the @handle notation everywhere, so a user never sees the suffix.

Squatting, governance and hosting are probably hard problems, but seem solvable.

TLDs are pretty cheap (i think you can get one for 250K), so not a big deal.

I'm thinking that we could make different routing / resolution mechanisms in the same way we do different ones for .onion addresses: the resolver (say, browser) hits the _atproto DNS TXT record to figure out where the data is hosted.

A discussion I had with @pfrazee.com @bnewbold.net and @dholms.at at the conference that I wanted to dig as a community is a TLD for atproto handles.

Lots of challenges, but I think I'm looking forward to a world where I'm @goto (syntactic sugar for goto.handle) on the web rather than @sgo.to

Ah, interesting, it seems like I have created another did:plc identity here on surf, because I didn't want want to enter my bluesky password there ...

@mmccue.bsky.social the other thing that I liked about surf's onboarding is that it allows me to sign-up/sign-in exclusively by verifying my email address :) that's cool :)

I think you might like this here:

github.com/WICG/email-v...

Surf 's onboarding screen had me at the "minimize Elon musk setting" :)

I actually like Elon, but I appreciate the boldness :)

Worth my free advertisement :)