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

Preserve message order when bridging from Telegram to Matrix #505

Closed
tulir opened this issue Aug 1, 2020 · 1 comment
Closed

Preserve message order when bridging from Telegram to Matrix #505

tulir opened this issue Aug 1, 2020 · 1 comment
Labels
blocked This issue requires some other issue to be fixed first enhancement New feature or improvement

Comments

@tulir
Copy link
Member

tulir commented Aug 1, 2020

Currently the bridge processes incoming messages in parallel and doesn't care about message order at all. This means that groups of forwarded messages, image albums and even normal messages may be bridged to Matrix out of order.

The solution is enabling sequential_updates=True in TelegramClient, but before that, media uploads need to become asynchronous (so that a big file being bridged doesn't block all other messages). Asynchronous media uploads while preserving message order requires matrix-org/matrix-spec-proposals#2246.

@tulir tulir added blocked This issue requires some other issue to be fixed first enhancement New feature or improvement labels Aug 1, 2020
@JuniorJPDJ
Copy link

What if you just edit message after sending a file?
It would probably break other things like facebook bridging, but it seems like pretty good workaround.

@tulir tulir closed this as completed Jan 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked This issue requires some other issue to be fixed first enhancement New feature or improvement
Development

No branches or pull requests

2 participants