alternative handles inaccessible, despite appearing in the did doc #179

closed

opened by

zenfyr.dev 4 months ago

my did:plc document declares multiple handles with @bsky.melontini.me being the main one.

  "alsoKnownAs": [
    "at://bsky.melontini.me",
    "at://melontini.me",
    "at://me.melontini.me"
  ],

bsky.app correctly resolves the handle like so: https://bsky.app/profile/melontini.me while here on tangled only the first handle is resolved, resulting in this https://tangled.sh/@melontini.me leading to a 404.

oppi.li 4mo ago

please see the discussion here: https://tangled.sh/@tangled.sh/core/issues/130#706201, TL;DR: atproto spec considers only the first handle to be valid.

https://atproto.com/specs/did#did-documents

oppi.li 4mo ago

The current handle for the DID is found in the alsoKnownAs array. Each element of this array is a URI. Handles will have the URI scheme at://, followed by the handle, with no path or other URI parts. The current primary handle is the first valid handle URI found in the ordered list. Any other handle URIs should be ignored

Labels

None yet.

area

None yet.

assignee

None yet.

Participants 2

AT URI

at://did:plc:rjhjcb3rgdsmdr6ykywuh63z/sh.tangled.repo.issue/3lweorv6pho22