It was just last year that re-found my little black book from the late 90’s and 2000’s with all my accounts from back then AIM/ICQ/Yahoo, shit there was even a /. account number sub 100,000 that I couldn’t log into any more

surly the total entropy in the room will stay the same?

I would feel like crap if I hit 37, normally sit at 36.6/36.7 where one ok our kids always seems to sit at 37.2.

No I’m not going to duckduckgo that for you

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 :(

from the photos that I saw thismorning she had also dropped a bow anchor, my thoughts are if this was done when the bow had already began its drift to starboard that could have swung the stern even more to port.

At least they called in in