You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per https://github.com/bluesky-social/atproto/blob/main/packages/pds/src/handle/reserved.ts, I cannot have a handle like @blog.mydomain.tld. This seems like a bit much? I can certainly understand why these reservations exist, but I think that some of them should be relaxed for non-bsky.social domains. 'bot' is another weird one to block out; seems like an obvious way to identify automated posting bots?
The text was updated successfully, but these errors were encountered:
That list is intended for folks doing open-registration services, where users can pick their own handle. We should probably make it optional/configurable for folks who are simply self-hosting or have a very small group/cohort of accounts.
In the meanwhile, you might be able to set any handle you want using a "custom domain handle", even if using the same domain suffix. You would chose any random handle to start, then change handle to a custom domain handle.
Per https://github.com/bluesky-social/atproto/blob/main/packages/pds/src/handle/reserved.ts, I cannot have a handle like @blog.mydomain.tld. This seems like a bit much? I can certainly understand why these reservations exist, but I think that some of them should be relaxed for non-bsky.social domains. 'bot' is another weird one to block out; seems like an obvious way to identify automated posting bots?
The text was updated successfully, but these errors were encountered: