It was always pretty bad, musk just made it worse

I have a 5900x (zen3), and apparently I got a bit unlucky with the silicon and ended up with a CPU that’s slightly unstable at its stock voltages and stock boost clock. The system would freeze and reboot randomly, and the bios would report an MCE error. This crash could be reproduced with near 100% success by doing sha1 hashing specifically for some odd reason. This is not a Linux issue, it’s a hardware defect.

It may be an Asus motherboard specific thing, but I found a workaround by going to the bios settings, precision boost overdrive, and increasing the voltage scalar to like 7. Now it’s been two years and I have only ever had it happen once since I changed that, so I’m happy.

Also, if you happen to be learning Japanese, Chinese, or Korean, check out https://github.com/themoeway/yomitan

Facebook may be evil but I don’t think they’re anywhere near “inject malware into global supply chains to push adoption of a public engineering side project that they don’t directly profit from and most executives don’t care about” level of evil. Is it possible? Sure anything is possible, but that is wildly beyond many many more plausible explanations and there’s zero evidence leading us down this path. And why would they go through the trouble of backdooring zstd, which has a highly observed codebase, when they just successfully backdoored lzma because it didn’t have a lot of maintainers?

While it’s true that zstd is commonly favored for having “good” compression at blazingly fast speeds, which is useful on the web and on servers, Zstd 's max compression setting (zstd --long -19) is actually within about 5% of LZMA’s but faster, so it replaces most use cases of LZMA except when that extra 5% (and that’s not even constant; some inputs are even better on zstd) really does matter at all speed cost

The first 3 seem incredibly far-fetched.

• What exactly does Facebook gain from more people using zstd, other than more contributions and improvement to zstd and the ecosystem (i.e. the reason corporations are willing to open source stuff).
• Why do you consider zlma to be loved among pirates and hackers and zstd not to be, when zstd is incredibly popular and well-loved in the FOSS community and compresses about as well as lzma?
• Every person in the world uses both lzma and zstd extensively, even if indirectly without them realizing it.

I think it’s likey that, of all the mainstream compression formats, lzma was the least audited (after all, it was being maintained by one overworked person). Zstd has lots of eyes on it from Google and Facebook, all of the most talented experts in the world on data compression contributing to it, and lots of contributors. Zlib has lots of forks and overall probably more attention than lzma. Bz2 is rarely used anymore. So that leaves lzma

Goldendict-ng

I already force Wayland global for SDL games because the xwayland one has a horrible stutter while the native Wayland works flawlessly. Making it the default sounds reasonable to me. If specific programs don’t work with it, they can override it

At its highest compression setting (zstd -T0 -19 --long), it’s about the same as lzma in compression ratio (varies a bit from file to file though), but slightly faster to compress, and much much faster to decompress. Decompression speed is not significantly affected by the compression setting (though compression speed is) and is usually at least a few hundred MiB/s to 1G+

If only that comment contained a link explaining exactly what it is…

It’s the spectral emissions lines

They are enshittifying, separately from this issue though.

Spankbang

I’m more of a garden KDE user

It’s unencrypted and we know with certainly that the messages are stored by federal agencies and cell carriers. It also requires giving out one’s phone number which may be undesirable in some situations

So the two least secure online communication methods possible?

I’m skeptical of Braxman. For someone who is supposedly an expert on the topic, he’s made some pretty bizarre and incorrect claims, such as that an ordinary person can map someone’s ip address to an exact physical address

Does this imply they weren’t anonymizing it previously?

It can handle websites like filejoker and nitroflare, which are behind captchas and things like mega that require JavaScript or an API to serve downloads

Both are true. Brute forcing zips is also faster than brute forcing almost anything else. Other formats use key derivation functions like PBKDF2-SHA1 (hundreds of thousands of iterations of sha1) to slow down the calculation of the key from the password, but PKZIP does not do this. Brute forcing zips can be done at 10 billion passwords per second on a typical GPU, whereas rar/7z/keepass are only a few thousand per second.

Here’s an interesting research paper describing both the known plaintext attack and the standard brute force attack https://www.scitepress.org/Papers/2019/73605/73605.pdf

Zip uses very bad encryption that is vulnerable to a known plaintext attack. Do not ever use PKZIP encryption for any purpose https://github.com/kimci86/bkcrack