-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Option to disable rate limiting for a specific user #6286
Comments
you can poke things into the |
That should be documented somewhere. It's not even a footnote in the synapse docs. |
It would also be nice if this was exposed either in the config, or even better through the admin API. |
For a nice TLDR answer for those of us that were a bit confused what exactly to do: you need the full user name (e.g.
where |
Thanks @refi64! Any chance you'd want to add some of this information to the documentation? I didn't find anywhere off-hand to add it quickly though... |
Don't have a ton of time for that atm, but I'll keep that in mind!
…On Mon, Jun 22, 2020 at 6:35 AM Patrick Cloke ***@***.***> wrote:
Thanks @refi64 <https://github.com/refi64>! Any chance you'd want to add
some of this information to the documentation? I didn't find anywhere
off-hand to add it quickly though...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6286 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAM4YSPEIXQXDLUADIOD5FDRX46ZLANCNFSM4JGTIJVA>
.
--
Ryan (ライアン)
Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else
https://refi64.com/
|
the insert into needs single quotes!
|
This worked for me but afterwards the server required a restart for the changes to take place. |
This seems to have disabled the rate limiting for sending messages but it hasn't removed the rate limiting for sending invites. |
this will be fixed by #9711 |
... and the lack of documentation will be fixed by #9648 |
Moderation bots shouldn't be rate limited because they might have to deal with high volumes of spam.
The text was updated successfully, but these errors were encountered: