Post

There are some questions about this service, especially since it seems to be from Bluesky (the company): -> github.com/bluesky-soci... Is this supposed to be a generic atproto service? Does this "promote" or "ossify" the Blueksy account lexicon now deeply into atproto as the canonical "account"?

github.comGitHub - bluesky-social/account-info: https://account.infohttps://account.info. Contribute to bluesky-social/account-info development by creating an account on GitHub.

0 reposts4 likes

Nope. If you read the code, the JSON response shape already supports multiple profile record types. I don't have omnipotent knowledge of all profiles, so we'll need some community effort to add support for others i.e. tangled was the only other one I could think of off the top of my head

yo @anirudh.fi question for you: are you intending to publish sh.tangled.actor.profile records for real? This fails to resolve, but I do see you have a record pdsls.dev/at://did:plc...

But as I said in another thread, the question on my mind (which is why I haven't announced this yet) is how do we let the user pick which record type as the default for this service so we can get the gravatar-for-atproto experience I desire

Ah it just hit me Yes we should allow the user to choose their own via publishing a info.account record, but we should just sort chronologically amongst all known profile record types and pick the oldest by date if they haven't manually specified

I also have questions, which is why I haven't announced it yet - obviously as-is this isn't finished. I'm not done designing and building it yet

My question is the same as you: how do we declare and allow the user to choose their own default profile? Perhaps a info.account.preference.self record that allows the user to specify the NSID of their preferred profile record type? Something of that nature, I'm not sure of the mechanism yet