Awesome! Win-win.
Comment on [PSA] Watch for the antiyanks troll and consider adjusting your rate limits
Sal@mander.xyz 2 days agoSo, ultimately my problem was that I was trying to set all of the limits to what I thought were “reasonable” values simultaneously, and misunderstood what ‘Message’ meant, and so I ended up breaking things with my changes without the reason being obvious to me. I looked into the source code and I can see now that indeed ‘Messages’ refer to API calls and not direct messages, and that there is no ‘Direct Message’ rate limit.
If I let ‘Messages’ stay high I can adjust the other values to reasonable values and everything works fine.
Thanks a lot for your help!! I am surprised and happy it actually worked out and I understand a little more 😁
BlueEther@lemmy.nz 2 days ago
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?
admiralpatrick@lemmy.world 2 days ago
If you have DB access, the values are in the
local_site_rate_limittable. You’ll probably have to restart Lemmy’s API container to pick up any changes if you edit the values in the DB.BlueEther@lemmy.nz 2 days ago
Thanks:
UPDATE local_site_rate_limit SET message = 999, message_per_second = 999 WHERE local_site_id = 1;Sal@mander.xyz 2 days ago
Sorry, I went to sleep. Glad you were able to sort it out 😄
BlueEther@no.lastname.nz 1 day ago
All good, taught me again not to rely on chatGPT. I even said I needed to find the right BD table and field and it lead me down a rabbit hole of editing config/env files
Fuck AI
Sal@mander.xyz 1 day ago
Haha, yeah, trusting ChatGPT with how to manipulate the database and change config files is a risky move 😆 I did use it myself to remind me of the postgresql syntax to find and alter the field.