People are complaining that an advanced fill tool that’s mostly used to remove a smudge or something is automatically marking a full image as an AI creation. As-is if someone actually wants to bypass this “check” all they have to do is strip the image’s metadata before uploading it.

deleted by creator

The notice itself isn’t malware, but I’m not sure on the cause. For some reason the Lemmy web client occasionally tries to cache a metric fuckton on iOS Safari (and probably elsewhere but it happens silently), which sounds like something for the devs to look into.

Generally, Lemmy’s 100x better in stability and speed than it was a couple months ago when a bunch of new people started working on it, but before then it was the side project of a handful of people and it showed. EG - The infamous, three-year-old Hexbear instance managed to have the entire picture side of it go down for a couple days because someone uploaded an absurdly large, extremely low quality photo of a North Korean soldier on it. So, there are probably still some issues like that kicking around.

That’s literally what concentration camps are. Points where you “concentrate” a population you’re trying to control.

Outright murdering the people you have in them was a Nazi death camp thing, but the Brits were probably most famous for using them before that while attempting to suppress colonial rebellion.

It can also be used as a form of semi-covert harassment. For example, in an early instance, every bit of content posted by or in support of transgender people would get hit by a barrage of downvotes from brigaders using otherwise inactive accounts. Hard to moderate that without just disabling downvotes entirely.

They also originally thought they’d have it update in real time which was a bit of a mistake. When you’re running a small test instance it’s kinda neat if comments and posts pop up as they’re made, but the reality of that is a scroll jacking nightmare.