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.

Sign up for GitHub

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

Jump to bottom

A bsky > fedi reply was delivered successfully, but not the deletion of that reply #1530

Closed
CurrentBias opened this issue Nov 20, 2024 · 2 comments
Closed

A bsky > fedi reply was delivered successfully, but not the deletion of that reply #1530

CurrentBias opened this issue Nov 20, 2024 · 2 comments
Labels
see other The issue was a duplicate or was fully merged into another issue.

Comments

@CurrentBias
Copy link

Hey, I appreciate you getting back to me so quickly regarding the blocking issue I had. I've got another weird one that I'm hoping isn't the result of me overlooking something:

From the feed for my bluesky account, you can see that I replied to a post from the bridged version of my fedi account, and then deleted it. The reply says it was delivered successfully, but the deletion was not, and as a result, the reply from the bridged version of my bluesky account is still in the fedi thread 17 hours later. I am wondering if this has to do with the unfollow and refollow activity before and after. Currently, the bluesky account is following the bsky > fedi bridge.

Thanks again
@Tamschi
Copy link
Collaborator

Tamschi commented Nov 21, 2024

This is likely #1361. Deletions can currently be missed too easily if they happen quickly after making the post.
Does that seem like it would fit or was there a longer delay between your actions?

@snarfed
Copy link
Owner

snarfed commented Nov 27, 2024

Duplicate of #1361

@snarfed snarfed marked this as a duplicate of #1361 Nov 27, 2024
@snarfed snarfed closed this as not planned Won't fix, can't repro, duplicate, stale Nov 27, 2024
@Tamschi Tamschi added the see other The issue was a duplicate or was fully merged into another issue. label Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
see other The issue was a duplicate or was fully merged into another issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Tamschi @snarfed @CurrentBias