Skip to content

fix: Don't add a tombstone for a reaction if the original message didn't arrive yet#8225

Draft
Hocuri wants to merge 7 commits intomainfrom
hoc/dont-tombstone-orphaned-reaction
Draft

fix: Don't add a tombstone for a reaction if the original message didn't arrive yet#8225
Hocuri wants to merge 7 commits intomainfrom
hoc/dont-tombstone-orphaned-reaction

Conversation

@Hocuri
Copy link
Copy Markdown
Collaborator

@Hocuri Hocuri commented May 8, 2026

Alternative to #8181

iequidoo and others added 7 commits May 1, 2026 07:15
…sage isn't found

A reaction may arrive earler than the referenced message in case of multi-transport. By not creating
a tombstone we still can receive it later on another transport.
This way if the self-MDN isn't applied successfully, it can be received again and retried.
@Hocuri Hocuri marked this pull request as draft May 8, 2026 14:42
@iequidoo
Copy link
Copy Markdown
Collaborator

This approach leads to adding bool return flags to several functions, that's why it's common to use typed errors or error codes (e.g. in C) instead.

Another option is to not add a tombstone in the default code path, but in separate paths after all necessary checks are done, but probably that will be even more complex.

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

Successfully merging this pull request may close these issues.

2 participants