The problem is not the RSA math itself but that it is both extremely slow and implementing it is particularly susceptible to bugs and side channel attacks https://blog.trailofbits.com/2019/07/08/fuck-rsa/

The article on theregister stated

Also inside the uploaded source code was some GPL 2 source code, which renders the not-very-open WCL moot.

Winamp published their code as “open source”. Problem is…

1. It wasn’t open source, it was proprietary but you can see the source code.
2. Their custom license didn’t even allow forks, which is against GitHub TOS
3. The codebase apparently contains proprietary code from third parties that they don’t have the right to relicense.
4. The codebase apparently contains GPL code from third parties that they probably didn’t have the right to make proprietary in the first place

Accessing printers? Resolving hostnames of internal hosts? I can’t imagine having a lan without mDNS

I’ve never had any issues getting mail delivered to major providers

Out of 4,037,953 GitHub user profiles with email addresses, we were able to identify 1,426,121 (35.3%) of them as men or women through their public Google+ profiles.

Could be a confounding variable in that the type of people who reveal their gender publicly might differ from those who don’t in some way that is also related to their contribution quality

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

It’s useful for security researchers to collect and analyze what the newest attack bots are trying to do, in order to learn how to defend against it and study the malware they drop. There are some cool videos on YouTube about decompiling malware dropped by the bots.

Maybe try Stash, it has gallery support too https://github.com/stashapp/stash

Also, what about jellyfin itself? It also supports photos

Lots of malware gets hosted using dynamic DNS domains, so they (or more likely some bot) probably saw the domain frequently showing up in malicious activity and blocked it without understanding that it itself isn’t the source of the malicious activity.

You can use cryptsetup-reencrypt to encrypt an existing disk in place with LUKS. Then you just have to modify the initramfs/bootloader/fstab to point to the new configuration. See https://wiki.archlinux.org/title/Dm-crypt/Device_encryption#Encrypt_an_existing_unencrypted_file_system

Yomichan (primarily for Japanese but may also work for Chinese and Korean): https://github.com/FooSoft/yomichan

Yomichan itself is no longer maintained, but an actively developed but still beta fork Yomitan exists: https://github.com/themoeway/yomitan

Setup for Japanese: https://aquafina-water-bottle.github.io/jp-mining-note/