"Message" bucket is kind of a general purpose bucket that covers a lot of different endpoints. I had to ask the lemmy devs what they were back when I was adding a config section in Tesseract for the rate limits.
These may be a little out of date, but I believe they're still largely correct:
That's a consideration, yeah,, but they'd have to all be hitting lemmy.zip (your instance) and all from the same /32 IPv4 address.
(AFAIK) CG-NAT still uses port address translation so there's an upper limit to the number of users behind one IP address. They also are distributed geographically. So everyone would need to be in the same area on the same instance to really have that be an issue.
The more likely scenario would be multiple people in the same IPv4 household using the same instance. But 20 comments per minute, divided by two people in the house would still be 10 comments per minute. That's still probably more than they could reasonably do.
Edit: You mentioned T-Mobile internet. T-Mobile is pretty much all IPv6 with IPv4 connectivity via CG-NAT. lemmy.zip is also reachable over IPv6, so in that situation,it would try IPv6 first and CG-NAT likely wouldn't even come into play.
$proxy_add_x_forwarded_for is a built-in variable that either adds to the existing X-Forwarded-For header, if present, or adds the XFF header with the value of the built-in $remote_ip variable.
The former case would be when Nginx is behind another reverse proxy, and the latter case when Nginx is exposed directly to the client.
Assuming this Nginx is exposed directly to the clients, maybe try changing the bottom section like this to use the $remote_addr value for the XFF header. The commented one is just to make rolling back easier. Nginx will need to be reloaded after making the change, naturally.
Yeah, you are setting it, but that's assuming the variable $proxy_add_x_forwarded_for has the correct IP. But the config itself is correct. Is Nginx directly receiving traffic from the clients, or is it behind another reverse proxy?
Do you have a separate location block for /api by chance, and is the proxy_set_header directive set there, too? Unless I'm mistaken, location blocks don't inherit that from the / location.
I replied to your other comment, but most likely cause is the API server not getting the correct client IP. If that's not setup correctly, then it will think every request is from the reverse proxy's IP and trigger the limit.
Unless they're broken again. Rate limiting seems to break every few releases, but my instance was on 0.19.12 before I shut it down, and those values worked.
Not sure. I had mine set to 20 per 60 for a long time without issue.
Most likely cause would be the Lemmy API service not getting the correct client IP and seeing all API requests come from the reverse proxy's IP.
Are you sending the client IP in the X-Forwarded-For header? Depending on how your inbound requests are routed, you may have to do that for every reverse proxy in the path.
So, a 'Comments' Rate limit: 10, Per second: 60, means a maximum of 10 comments per minute, correct?
Correct, per client IP.
Maybe the reason you see 99999999 is due to troubleshooting
Could be. I try not to speculate on "why" when I don't have access to the answer lol.
I don't recall any of them being from mander (unless they were dealt with before I started testing?), but thanks for taking preventative measures :)
I don't know what 'Antiyanks' is
It's the codename for a particular long-term troll and is based off of their original username pattern (which they still use sometimes). I have reason to believe it's also the same troll that used to spam the racist stuff in Science Memes.
These are most of today's batch (minus the JON333 which was just a garden-variety spammer that made it into the last screenshot).
Lemmy's API doesn't have a direct way to do that, unfortunately.
Tesseract (web-based lemmy app) used to have that before I took it out. After the ranking metrics were removed from the API, it was hard to sort them other than by new/old or by score. When you have a mix of active and inactive communities, it didn't work great without the ranking metrics being there.
You can still group communities, but only for organizing them or (in the dev branch/next version) applying filter policies to communities in that group.
I may revisit the idea if I can figure out a better way to generate/sort the custom feeds.
Oh, I was just jokingly salty that there were two articles covering fediverse clients and felt snubbed it didn't get so much as a mention in either despite having more features than all the ones that did get mentioned. Again, jokingly salty, and not actually upset lol.
The discussion you're chiming in on wasn't even about this article; it was about one from a week ago. And now you're butting in with the wrong context, making unfounded accusations, jumping to conclusions, and throwing out personal attacks.. Keep up or keep out.
Mod removals should link to this automatically and be more transparent for why comments were removed in the first place
I linked to the modlog through Lemmy World's instance of Tesseract. I'm the dev of that UI, and I agree with you that removal reasons should be more accessible.
A version or two ago I built in a feature to automatically resolve the removal reason and append it where the comment would be, right there in the comment section. If that's disabled, there's a button to take you to the modlog for that item.
If Tesseract isn't your cup of tea, maybe ask the dev of your client to add a similar feature.
I'm done. I'm fucking done. You've moved the goalposts so far beyond the original that I don't think we're even in the same state we started out in.
Bottom line: You were espousing dangerous rhetoric given how flippantly people around here resort to calling others nazis (the subjects of articles and other users both). You can't just deem/call someone a nazi and use that as an excuse for "anything goes". I've explained how that is a dangerous cocktail.
Say what you will. If it's in violations of the rules, it'll probably get modded. If the behavior repeats, you may get a ban. That's not specific to you; it applies to everyone. In no way are mod actions here to be interpreted as anything other than maintaining a civil atmosphere and adherence to the community rules and the LW TOS.
Don't like it? Go over to YPTB and whine and spin another tall tale about how mods here are fascist bootlickers because we won't let people screech for violence. Or you can go find another community that allows that kind of bullshit. Frankly, I don't give a fuck.,
I've explained the rationale behind the mod actions clearly and more than once. If you don't get it by now, I'm not going to entertain you any further.
One of these days your mom's gonna stop paying for your Mullvad subscription. Whaddya gonna do then?