Has anyone ever tested those red hats for lead content?

There was an episode of QI where Stephen was playing with a device where you point its directional microphone at someone, and it plays their voice back with a slight delay making it very difficult for them to speak. The guests had to try to read a children’s book aloud while he pointed it at them. None of them except Alan could do it.

I would like to buy one of those devices lol.

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’.

I did test a few posts with a lot of removed comments (both on my instance and Lemmy World), and the overhead wasn’t terrible since scoping the modlog to just the comment ID is pretty lightweight. Since HTTP/2 is pretty common (which can re-use connections), there’s not overhead of additional TLS handshakes slowing things down.

From a network traffic standpoint, Gzip compressed JSON is pretty negligible in the grand scheme of things.

!whitelistsilver

Nothing for or against the content, OP, but removing since it violates rule 1 which prohibits political posts.

That’s good news (hopefully). Thanks!

Will keep an eye out, but community is remaining locked until the clarifications are published and deemed acceptable.

I explained that in another comment: https://lemmy.world/comment/14408131

My stance has always been keep the server/instance rules generic / non-micromanaging and let the communities do what they do (so long as they’re in compliance with the generic server rules). That’s pretty much been LW’s stance until yesterday.

Re: fiefdoms

Many times I’ve seen new communities spring up as alternatives and people slowly (sometimes rapidly) moved over organically. That’s one of the big benefits to the Fediverse. My experience has been that, letting the Fediverse do what it does, the problems will generally sort themselves out as bad mods/instances are identified and avoided with alternatives springing up to fill the gap.

I’m with you in spirit, but I can’t and won’t endorse that kind of behavior (not even saying that to cover my ass; I’m truly against it).

However, should that occur organically (and it will), feel free to shine a “I told you so” spotlight onto it.

As I understand it, yes, that is the intent of the policy. However, as-written and presumably as it is to be enforced for all mods LW-wide, it has wide-reaching implications with worse side-effects.

Basically, the proper tool is a scalpel and they brought out a machete.

I never said I was against the goal they were trying to achieve, just the means by which they’re using to achieve it.

I’m mostly with you, though with a much more strict stance against allowing misinformation/conspiracy/etc. On that:

The beauty of the fediverse is that I also have no problems with someone setting up a competing community that takes a much less tolerant perspective and has a rule that participation is conditional on agreement to certain perspectives.

That’s what this new moderation policy abolishes: That competing community is now apparently required to platform misinformation, propaganda, et al while also being more or less required to spend time refuting every claim lest it stand unchallenged. As I said in the announcement post, it’s holding the doors open and saying “no, after you” to gish-galloping the mods and platforming every crackpot conspiracy, propaganda, “civil” hate speech, etc so long as they’re civil and not spamming it.

Yeah, the Fediverse allows for “just moving to another instance” but for the largest Lemmy instance to force a “both sides” stance on its entirety is a slap in the face.

Vote manipulation is common in Lemmy. While the actor described in that post has changed tactics (and that post barely scratched the surface), they certainly did not stop. All they need to do is boost the misinformation and downvote the rebuttals when previously, the misinformation would just be correctly modded.

Yep, sure do! But only on my own instance in accordance with our polices; communities I moderate elsewhere are modded according to those instances’ rules and TOS.

If someone does nothing but give out downvotes (the upvotes-given to downvotes-given ratio threshold for the automated ban is quite generous), then they’re contributing nothing but negativity and shitting on things for everyone else. If everything here displeases them so much, they can and should go somewhere else.

I stand by (and have reviewed) every automated “Mass downvoting” ban my automod has issued.

It definitely does not seem like a well thought out solution for sure.

It’s an option, sure. But (at this point anyway) it’s more about making a statement and trying to bring visibility to the horrible side effects of this new policy.

I’m not trying to burn bridges, lol, merely shine a light and hope the LW Team sees it.

That’s basically the long-form of how I feel about it. Honestly, I was having a hard time staying composed while I responded to the announcement thread; I was livid and absolutely shaking.

A sad two sentence story…of my life lol

I had to resolve the post, but it’s there now.

I don’t notice a lot of stuff disappearing during federation with LW, but when I do notice it, I just un-upvote my comment and re-upvote it. Seems to kick it in gear. Never tried that with posts, but might work similarly.