Samuel
@samuel.fm
endgame: Bluesky PBC buys the .bsky TLD, we get bsky.bsky
1 3 23
Whyor we keep all the power for ourselves and make our handle simply "bsky"
2 14SamuelI like the idea that you get Twitter-style handles if you have the money and influence to purchase a TLD
1 8
shreyan (wise)brb registering `shreyan` with icann
1 3
David BuchananI might be totally imagining this but I vaguely recall the spec saying you need at least two levels (presumably to prevent confusion with twitter handles et al). lemme go double check...
1 5David Buchananyup
atproto.com/specs/handle
> there must be at least two segments
2 7Samuelbooooooo
1 2
The Doctor (Commissions open)Boo.bsky.bsky sounds good.
3Whythats silly. We should simply change the spec
1 10
bryan newboldresults in a collision with "local" handles in client UI.
we aren't using that much right now but wanted to reserve it.
2 5bryan newboldfor that matter what about @.
1Whywhat are "local" handles?
1 2bryan newboldif i'm on a PDS which provides `*.robocracy.org` handles to accounts, and I do `@hal` in my client, that could auto-expand to `@hal.robocracy.org` (hal as a "local" handle).
precedent is how DNS normally works, and fediverse. it is kind of a stretch and maybe a bad idea
3 10
WhyYeah that seems as-of-yet-undecided-on, neat feature idea though
1 3WhyI remember pitching paul on something like this (hiding the .bsky.social bit on the app here) but he didnt like it back then (probably for good reason)
2 3Samuelinteresting that that is reserved as an option. I think it’s the right call to keep it in the spec, but not use it in the official app
1 2
Eurosky SebastianI will do so in @skeets-app.bsky.social mainly for accessibility reasons (creates a lot of audio „garbage“ when using a Screenreader) and only display custom handles.
2