Skip to content

Preserve message order when bridging from Telegram to Matrix #505

@tulir

Description

@tulir

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    blockedThis issue requires some other issue to be fixed firstenhancementNew feature or improvement

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions