Post

public service announcement: if you change your username from bsky​.social (e.g. @amk.bsky.social) to a custom domain (e.g. @april.social), please be aware that your original username will be returned to the pool and someone else can claim it.

36 reposts95 likes

sure it's probably not a huge problem now, but it will be for people with lots of followers with a lot of links that officially point to the old account.

that's not usually true, on the vast majority of platforms changing your handle makes it unavailable. if not forever, at least for a very long time.

not that I can tell at the moment. probably less of a problem while the social network is small, but definitely could be an impersonation problem as the network grows.

There was good discussion on allowing multiple domains and reserving domain equal to length of time it was active and also never letting custom domains go as long as it's verified and owned etc.

We'd basically need a domain usable as the primary authority, like bsky.social, where we could reserve our names + set the DNS TXT _atproto record to point to our DID, even if it's configured to use a vanity domain in the same way. DNS validation of identity by multiple domains

I think the goal is that there are several big domains not only .bsky.social and that ppl look at the whole domain as the user identity rather than assume mike or tom is the same person across all domains?

Yeah but say you move to workplace domain and want to go back and you don't have it available. There's definitely been discussion here on multiple domains and retention policies.

yeah definitely and makes sense for that use case... lol I posted abt this before, having journalists and professors w secondary pointers from each institution they're associated with as verification of the relationship

One consequence of this might be that if you get a big following with a bsky dot social domain and have concerns about impersonation, you might not really feel able to switch to custom domain

One nice feature of the AT protocol is that all links to a user profile (like an @-mention in a post) actually link to their underlying unique ID, not to their handle -- so if you change your handle, all the old posts still link to you!

I’m not sure this will be too overly big a problem. Bsky Social, even if considered a namespace (it’s just a federated server) will become the Gmail address of the Internet. People’s unique handles will be tied to the complete address used to identify themselves. Also the at mentions all update.

okay sure but if I use @amk.bsky.social for years, cultivate a million followers and then move my handle, all the references to my handle that are all over the place are now wrong. it matters less when it's new, but makes it hard to change handles as the system grows.

The references on the AT protocol should, if I have read the spec correctly, all auto-update to your new handle. But, yeah, non AT protocol references and even external links would break. Sounds like a problem that the team should solve with pointer accounts. Or similar.

References in @-mentions are to your permanent DID underneath, not the string, so it does go to the right spot. Of course there are other places like hard linking to the URL etc Normalizing bsky as temp names!