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

bridgev2: Add way to process backfilled edits #293

Open
purpshell opened this issue Oct 11, 2024 · 0 comments
Open

bridgev2: Add way to process backfilled edits #293

purpshell opened this issue Oct 11, 2024 · 0 comments
Labels

Comments

@purpshell
Copy link
Member

The situation

As of v0.21.0, the bridge is unable to handle message edits that happened in the past. Edits are not supposed to be in the message table. The network connector is unable to differentiate between a normal message and edit, which leaves all messages, edits and original in the table.

Suggested Solution

The current suggested solution is to process edits differently in FetchMessagesResponse. By adding a Edits property, and putting all edits in there, the network connector can drop "legacy"/non-infinite backfill messages containing edits without impacting the database.

@purpshell purpshell added the bug label Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

1 participant