bnewbold

For handles, you should be able to see this in the account profile view, which shows "DID history", at least for did:plc accounts, including handle changes. For display name and...

Just to make sure i've commented consistently on all these threads: we definitely want to support additional curves *registered as verified credentials*, did not realize how restrictive things were until...

I think we have resolved the underlying issue with this change: - https://github.com/did-method-plc/did-method-plc/pull/101 - https://github.com/bluesky-social/atproto/discussions/3928

In case you haven't seen it, please see the OAuth specs for details on the localhost/dev mode: https://atproto.com/specs/oauth#localhost-client-development

hrm, the basic account login should not usually require an email token. do you have "email 2FA" enabled for your account? is your account email verified? I may not have...

I think the root issue here was addressed; please re-open an issue in the new repo if you still have problems: https://github.com/bluesky-social/goat

I've had something like this on my TODO list for a while! I haven't dug in super deep to your implementation here, but I really like the HTTPie "interface" and...

Yes, we definitely intend to support OAuth clients in the indigo SDK, and have a started a bit of work on that in various branches.

This is shipped now. It uses the `indigo:atproto/atclient` `APIClient` struct not `xrpc.Client`, but they are pretty similar and can both be used with codegen types. There is a quickstart at:...

You should be able to log in for most actions, just potentially not account-critical actions like generating a PLC token. This blog post describes account migration and mentions that the...