-
Notifications
You must be signed in to change notification settings - Fork 39
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
Try harder to delete bridged accounts when the source account is deleted #1304
Comments
Ooh, thanks for reporting! Looks like we currently delete Bluesky bridged profiles when someone opts out, but not when they delete their fediverse account. We should! Should be straightforward. |
MVP 🙏 cheers! |
Actually, I take it back. The immediate problem here was that when Bridgy Fed followed you back from @bsky.brid.gy@bsky.brid.gy, c.wtf choked on that Since c.wtf never got that follow, it never started sending Bridgy Fed your activities, including the |
Here's the
|
Same issue here. I added However, the Bluesky account still exists : / It was a few minutes ago, but I was hoping not to leave the |
so that User.enabled_protocols is still populated during deliver for #1304
OK, added an integration test for fediverse => Bluesky. If a fediverse account accepts @bsky.brid.gy@bsky.brid.gy's follow, we correctly deleted them. @breadguyyy and @cuducos, I've deleted your bridged Bluesky accounts. Remaining work here is to add an integration test for web too. |
Done! |
Awesome ✨ Thank you so much : ) |
MVP 👍 |
https://bsky.app/profile/breadguyyy.c.wtf.ap.brid.gy
the original account no longer exists for this one
The text was updated successfully, but these errors were encountered: