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

"accepted #follow-back-ht..." is listed as waiting to be delivered, and a profile hasn't been made on Bluesky #1412

Closed
killthealias opened this issue Oct 23, 2024 · 4 comments
Labels
bug User-facing breakage and reliability issues within Bridgy Fed. see other The issue was a duplicate or was fully merged into another issue.

Comments

@killthealias
Copy link

Hello!
I'm trying to have my account bridged to Bluesky, but when I check it here https://fed.brid.gy/ap/@[email protected] it simply says that the follow back request is waiting to be delivered and that nothing else is synced. The account doesn't have a presence in Bluesky. Is there anything that can be done about this?
Thanks!

@Tamschi
Copy link
Collaborator

Tamschi commented Oct 23, 2024

The software is a relatively recent vanilla Mastodon that I think there aren't any known issues with.
The account fulfills the spam filter requirements and never blocked the bridge account according to the activity log.

Additionally, the DID Doc shows up in atproto-browser, but the collections can't be fetched: https://atproto-browser.vercel.app/at/riley.fiera.social.ap.brid.gy

Looks like a new bug to me. Thanks for reporting!
Is it correct that bridging this account never worked before?

@Tamschi Tamschi added the bug User-facing breakage and reliability issues within Bridgy Fed. label Oct 23, 2024
@snarfed
Copy link
Owner

snarfed commented Oct 23, 2024

Looks like this account blocked @[email protected] back on 9/10, which tombstoned the ATProto repo, and that can't currently be undone. Background in #1130. We now disable Bluesky accounts a different way that can be undone, and we're working on a way to bring back old tombstoned accounts like this, but I don't have an ETA for that yet.

Also, #1330 would add UX that would help people understand when this has happened.

(Thanks for investigating @Tamschi! We don't currently show blocks in activity logs on user pages.)

@Tamschi
Copy link
Collaborator

Tamschi commented Oct 23, 2024

(Thanks for investigating @Tamschi! We don't currently show blocks in activity logs on user pages.)

Ah, sorry about the confusion! I'll keep that in mind.

@Tamschi Tamschi added the see other The issue was a duplicate or was fully merged into another issue. label Nov 3, 2024
@Tamschi
Copy link
Collaborator

Tamschi commented Nov 3, 2024

@killthealias I'll close this since the underlying issue that caused this was solved elsewhere, but your account is still stuck until re-enabled manually. You can request this in #1446 or via email (see #1446 (comment)).

@Tamschi Tamschi closed this as not planned Won't fix, can't repro, duplicate, stale Nov 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug User-facing breakage and reliability issues within Bridgy Fed. see other The issue was a duplicate or was fully merged into another issue.
Projects
None yet
Development

No branches or pull requests

3 participants