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
I think leveraging the alsoKnownAs array in an account's DID document would be the best solution for this. Adding these links to the document is trivial, and lets the web app know what <link rel="me" href="..."> elements to put on a user's profile page. Additionally, having the app verify these connections and display them on a profile would effectively serve as an Open Web method for user verification. ORCID profiles, which are for verified researchers, already use rel=me on their outbound profile links. Verifying that this connection goes both ways and showing it to the app user would be leagues more effective and more true to the spirit of Bluesky than adding a centralized verification system a la Twitter check marks.
There is an existing tool for showing the alsoKnownAs entries and their verification status by the way: verify.aviary.domains The linked page shows my DID document's connections, including my GitHub and personal website. You can check my GitHub page for the link back to my Bluesky profile, and use the element inspector to confirm it has the rel=me attribute; the same goes for my website.
please add rel=me support
microformats.org/wiki/rel-me
there has been lots of discussion on it, but no official github post
this could be used in both verification of users, and for verification of social media profiles, and links
bluesky-social/atproto#2544 (comment)
The text was updated successfully, but these errors were encountered: