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

Fuck this government

In the last few days we have been right in the middle of this last weather bomb.

• Some 250mm of rain fell between 8- 12 hours
• The guy that died had a grandbane at our kids school, and died only a few KM from where we live
• The two bridges that have been all over social media, one is just along the road from us, and the other is probably less that 10 KM from here
• We have lost our water plant to flood damage - I've just plumbed the house to the rainwater that had been only used for the gardens until now
• Our neighbor has lost almost all his market gardens, they were right below the first bridge mentioned above
• There are photos of paddocks covered in minced up eels - there was that much stone and wood moving down the rivers

oh look pictures are working

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

No I'm not going to duckduckgo that for you

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