Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ATProto: run full handle resolution for ATProto.handle property #1659

Open
snarfed opened this issue Jan 2, 2025 · 2 comments
Open

ATProto: run full handle resolution for ATProto.handle property #1659

snarfed opened this issue Jan 2, 2025 · 2 comments

Comments

@snarfed
Copy link
Owner

snarfed commented Jan 2, 2025

Right now, when we store an ATProto user, we grab their handle from their DID doc's alsoKnownAs and store it in the handle property. That's generally ok, but when someone creates a new account and moves an existing handle to that new account, the old DID doc still has the old handle in alsoKnownAs, so when Bridgy Fed looks up the ATProto user with that handle, eg for Webfinger, it sometimes gets the old DID.

#1201 is related, but not the root cause here. We need to change ATProto.handle to do full, bidirectional handle resolution. Sigh, ok.

@lucidillusions
Copy link

@snarfed would this also solve the issue #39 where the bridge fails if I rename the bridged (pixelfed) account on bsky?

(or is this a new thing, since now bsky will start reserving our original bsky handle when we do custom domain - so it resolves that?)

@snarfed
Copy link
Owner Author

snarfed commented Jan 5, 2025

@lucidillusions you mean, if you change your Bluesky handle? That's #1074, right? The status there is mostly that we're blocked on fediverse software handling username changes. This issue is largely unrelated afaict.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants