Black Xanthus

Oh lookit! Trying to fleece people using your product in good faith backfires.

Who’d have think?/s

An incredibly well-written piece. Even if the subject matter and conclusion are chilling.

I don’t know if there is, but it feels like the email protocol problem.

Like, while the protocol sucks in many, many ways, it would take something revolutionary to replace it because it’s everywhere.

It’s been around so long that everything talks the protocol, the binaries that handle it are mature and stable.

Then you have to ask: what would you replace it with? It does the job it’s designed to do very well. There’s nothing the matter with the protocol, and it’s still fit-for-purpose.

That doesn’t mean there aren’t problems - spam, bad actors, and so on, but ultimately that’s not the fault of the protocol (though, maybe, for email, people have been arguing about protocol-level ways of dealing with spam for years).

I don’t have an answer, but I feel like there should be one, but I doubt the is.

However, unlike Reddit, there’s alternatives. You might not like the community on @lemmy.world, but you might like the community on @anotherlemmythatmight.exist.

Because of the federated nature, communities will naturally fracture and focus. Here, a bad faith mod will just kill a community on instance a, and people will move to instance b.

We’ve already seen things happen like this under the banner of ‘free speech’, where people believe that free speech means free from consequences. If you think that, there are plenty of instances out there. Lemmy.world isn’t one of them.

This means that you can find your favourite community in places with different server rules. Which means it will be the community - the people, the mods, the knowledge, that grows one, not just the fact the names taken.

The last time I saw this was on a slow-failing HDD.

Check a quick fsck might get you a few answers. You can find more info in the Linux manual. It could just be one or two bad blocks that you can recover and fix the problem (though, ofc, it’s time to backup your data).

The other, slightly unusual time I’ve seen it is with mixed RAM. 16gb made of 2x6g and then 2x4gb did some real odd things to the system. If it’s not the disk, and your box will boot with one stick of ram, try it to see if it fixes the issue. It could be that your RAM speeds are off (or your like me and just put two sticks you had lying around, and it basically worked until it didn’t).

An outlier, that I’ve not seen on modern machines is io/wait for a CD-ROM to spin up, even if your not accessing the CD-ROM. Normally caused by bad cabling. Based on the age of your machine, this is unlikely, but it might be worth unplugging devices to see if one is bad and not reporting properly.

This is, if course, assuming dmsg is empty

Final thought: see if your running SELinux. If you are, turn it off and try again. Those policies are complex, and something installed in a non-standard place could be causing SELinux to slow IO as it fills your logs with warnings.

Hope that helps,