Oh damn, atproto-browser requires you have a handle attached to your did doc. I think its totally valid to not have a handle on atproto right? I should fix that
Comments
Log in with your Bluesky account to leave a comment
yeah, pretty sure you can just nuke all your alsoKnownAs entries, or even use non-at:// entries instead.
however, I'm pretty sure that the official PDS implementation *specifically* requires the first entry to be an at:// handle, otherwise it makes your account read-only (I think?)
Having accidentally had the first item *not* be at://, all it did was eventually show "Invalid Handle" on that account. This was on a did:web, mind you, but the implementation is practically the same after the DID is resolved
I got curious about it too & spent a good while going through the PDS & PLC directory implementations to figure out all the requirements not mentioned in the spec
I'm pretty sure your account goes read-only if your handle is unverified, at least I feel like that was the case before?
As mentioned in the other comment, it might have been a thing I heard in the past, or it's only enforced at the client level - dunno, but the repo is probably not read-only. At the PDS level, the behavior between did:web and did:plc (after resolution) should be the same though.
I remember something about Bsky forcing people to update their handle if resolution fails, can't recall the source or context (in-app only? or is it "read-only" at the AppView level?), so yeah, I'm probably wrong regarding the read-only thing.
in other words, a custom PDS impl could lift those restrictions and let you use your account without a valid handle.
also, PLC spec says that alsoKnownAs are "URIs which indicate other names or aliases", so they aren't technically even required to be at:// URIs (which the PDS impl does require).
Comments
however, I'm pretty sure that the official PDS implementation *specifically* requires the first entry to be an at:// handle, otherwise it makes your account read-only (I think?)
I'm pretty sure your account goes read-only if your handle is unverified, at least I feel like that was the case before?
Suppose the easiest way would be to just create a test account, delete the at:// in a PLC op, and see what happens 😄
(also, the PLC thing in Rust sounds cool!)
also, PLC spec says that alsoKnownAs are "URIs which indicate other names or aliases", so they aren't technically even required to be at:// URIs (which the PDS impl does require).