Thanks, looks like I’ve got that.
FWIW, in my case, increasing the value for message in the rate_limit section of lemmy.hjson as well as removing the limit_req_zone parameter in the nginx config did the trick for yesterday’s traffic burst. I’ll probably put them back (or at least reduce them to saner values) once the spike dies down a bit.
Here you are: https://github.com/100millionbooks/lemmy-ui
Thank you all for the great work, and let me know if there’s anything more I need to do in order to properly comply with the license. I use the AGPL myself so I should’ve been more proactive about it.
I need to learn more about it and how it works. Part of the reason I picked Lemmy over other options was the possibility of federation.
What do you mean?
Yeah sorry guys, I was blindsided by the default Lemmy rate limits and was NOT expecting front-age HN so…it was down for like an hour :(
Should be good now though.
@nutomic@lemmy.ml I had the code up but recently shuffled my GitHub accounts so removed it.
Really I just commented out a bunch of things in lemmy-ui, but terms are terms, so I’ll get it up ASAP!
Ah thanks for the link! I was about to ask anyway. Actually the reason I even discovered this thread in the first place is that I came here looking for the thread you posted a few days ago about federation testing…then I saw this thread, replied, and forgot why I came here :D