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

Bsky users start following wrong account after receiving bridging message #1545

Closed
agharbeia opened this issue Nov 23, 2024 · 1 comment
Closed

Comments

@agharbeia
Copy link

I used to use my domain name as the handle for a normal, full BlueSky account.

Then 1) I created a bridge for my Mastodon account, then 2) mapped my domain to the bridged account via DNS record, then 3) instructed Bridgy to use my domain as the username, which seems to have succeeded.

Now, whenever a bridging message is sent by Bridgy on my behalf to someone on BlueSky, they start following my full, unbridged account instead of the bridged one.

I never managed to see what exactly is written in the bridging message sent to BlueSky users, because when I tried to, by requesting the bridging of my BlueSky full account to Mastodon, I got what's describe in #1544

It's as if the domain is still [cache?] mapped to my full BlueSky account somewhere! If so, it should be out of the scope of Bridgy, but I want to make sure that I'm not missing something pertaining to Bridgy.

@agharbeia
Copy link
Author

I'm closing this as "unconfirmed" for now, since the observation could be circumstantial, and the root cause could be undelivered bridging initiation messages, as described in #1548

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

1 participant