I would rather see a slashed tyre than a slow leak - you cant very well drive on a slashed tyre, but a slow leak just may cause someone’s death that just happens to be in the wrong place

as someone with their heavy goods, 10 ton behind a pickup is terrifying

If you have DB access, the values are in the local_site_rate_limit table. You’ll probably have to restart Lemmy’s API container to pick up any changes if you edit the values in the DB.

100 per second is what I had in my configuration, but you may bump that up to 250 or more if your instance is larger.

Fixed:

UPDATE local_site_rate_limit SET message = 999, message_per_second = 999 WHERE local_site_id = 1;

local_site_rate_limit

Thanks: UPDATE local_site_rate_limit SET message = 999, message_per_second = 999 WHERE local_site_id = 1;

Hi I think I set the messages too low as well and now no.lastname.nz is down, pointers on how to fix with no frontend?

how did you fix?

ok, I fucked up and now my instance is erroring :(