-
Notifications
You must be signed in to change notification settings - Fork 40
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
Fediverse accounts stopped being bridged to Bluesky #1038
Comments
For context, here are a few fediverse accounts that opted in a week ago that doesn't get bridged anymore: https://mastodonsweden.se/@doktorzjivago https://mementomori.social/@rolle And here are some fediverse accounts that opted in more recently, that still get bridged: |
Thanks for the report, and for the examples! I think I know what's going on here; I think it's related to some cases where we emit invalid ATProto records - #1015, #1016, #1007 - and the relay gets stuck on those repos and won't ingest new records for them. I expect this is the same root cause underlying the AP => Bluesky part of #1037. This will take some debugging and work to resolve, even with @mackuba's hugely helpful investigations so far, but it's very doable. High on my list of priorities.. |
Fixing https://bsky.app/profile/rolle.mementomori.social.ap.brid.gy isn't, though, and I'm not sure why. All of his recent posts have hashtags, and it's possible we're generating invalid ATProto records for those, but unlikely. Hrm. |
Yes I saw it worked again, very cool! |
Tentatively closing. Feel free to reopen or follow up if you see more examples, I can check if the relay hasn't re-indexed them yet. |
Lots of fediverse accounts opted in about a week ago. However, since about 3-4 days, nothing gets through to bluesky. The mirrored accounts are still there, but no posts, likes, comments, reposts or anything comes up on bluesky. Seen this on several accounts. However, accounts that opted in recently, today and yesterday, seem to bridge just fine.
The text was updated successfully, but these errors were encountered: