Edit 2025-01-13: LW has indicated they will be clarifying these rules soon. In the mean time, the community will remain locked until those are updated and deemed acceptable.
So the LW Team put out an announcement on new, site-wide moderation policy (see post link). I've defended, to many a downvote, pretty much every major decision they've made, but I absolutely cannot defend this one. In short, mods are expected to counter pretty much every batshit claim rather than mod it as misinformation, trolling, attack on groups, etc.
My rebuttal (using my main account) to the announcement: https://dubvee.org/comment/3541322
We're going to allow some "flat earth" comments. We're going to force some moderators to accept some "flat earth" comments. The point of this is that you should be able to counter those comments with words, and not need moderation/admin tools to do so.
(emphases mine)
Me: What if, to use the recent example from Meta, someone comes into a LGBT+ community and says they think being gay is a mental illness and /or link some quack study? Is that an attack on a group or is it "respectful dissent"?
LW: A lot of attacks like that are common and worth refuting once in awhile anyway. It can be valuable to show the response on occasion
I understand what they're trying to address here (highly encourage you to read the linked post), but the way they're going about it is heavy handed and reeks of "both sides"-ing every community, removing agency from the community moderators who work like hell to keep these spaces safe and civil, and opening the floodgates for misinformation and "civil" hate speech. How this new policy fits with their Terms of Service is completely lost to me.
I'll leave the speculation as to whether Musk dropped LW a big check as an exercise to the reader.
For now, this community is going dark in protest and I encourage other communities who may disagree with this new policy to join. Again, I understand the problem that is trying to be addressed, but this new policy, as-written, is not the way to do it.
That's a good point. I'll have to check the default values, but on my own instance, I have very conservative limits in place, and it hasn't proven to be an issue (so far?).
Unless it's changed since I wrote the online docs for Tessreact, the modlog is part of the "Messages" rate limit bucket which is/was something of a catch-all for endpoints that didn't fit elsewhere. Even in the default config, that bucket is the most permissive due to that.
I've been daily-driving my dev version with this feature enabled for a few days, and it hasn't been an issue so far (it only does a modlog lookup if a comment is removed, so not on every comment in the tree). It's also per IP, so unless a lot of people are behind the same public IP, I don't think it's going to pose an issue. I'd have to double check, but I think the most comments it loads in a batch is close to 100, so unless every comment has been removed, that would be the worst-case number of modlog fetches.
So it looks like I'll definitely want to make this feature toggleable even if it does end up defaulting to 'on'.