Open chuckwagoncomputing opened 1 year ago
It just occurred to me that it's probably limiting my account - because of the double-puppeting, the messages I sent are bridged using my account.
Could ratelimits be disabled in the register-user task?
Could ratelimits be disabled in the register-user task?
They cannot. You'd need to use one of the other ways
So it can only be fixed manually, and not by default?
Playbook Configuration:
The relevant portion of my
vars.yml
file looks like this:Problem description:
When mautrix-telegram tries to backfill a chat with a long history, it gets rate limited. Here's the error message:
I don't understand why this happens.
rate_limited:false
is in the config https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/4dda00dbc609b0b16b3d2090fc43eb314733eecb/roles/custom/matrix-bridge-mautrix-telegram/defaults/main.yml#L155 My understanding is that this is supposed to disable rate limiting for all users of this appservice, which should include the@telegram_*
users which mirror messages. Relevant Synapse code: https://github.com/matrix-org/synapse/blob/d53547352063c3e66302f7bdc40d7ac7270e605c/synapse/api/ratelimiting.py#L139Additional context Backfilling with MSC2716 wasn't working at all for me, so this is using the timestamp massaging mode of mautrix-telegram. The resulting history is scrambled, which I assume is a result of it being rate limited, as it works perfectly on chats with less history.