I don’t exactly consider Drew Devault a reliable or unbiased judge of character

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

Huh, I misremembered then. I stand corrected.

Notable though that there are specific countries (such as India) where adoption is far higher at 72%

Huh weird that it would be removed, that’s a fair comment.

For Web scraping and other activities by so-called “legitimate” companies to varying degrees, this may be the case. But for general bots, they are generally attempting to scan and probe the entire IPv4 range, since it can be exhaustively checked in a reasonable amount of time and the majority of IPs have hosts on them. Enumerating the entire IPv6 space is quite literally impossible without some external list of hosts known to exist, due to the number of hosts. This happens, but it’s a much higher hanging fruit for an attacker so far fewer will bother. So you generally see few to no continuous probes on things like sshd over IPv6 unless you have a domain name. I’m guessing a lot of bots (in botnets) are dumb old technology that doesn’t even have IPv6.

NAT was always a hacky workaround. And although it effectively ends up functioning as a firewall under normal usage when combined with a typical “drop invalid incoming packets” rule, it was not designed to be a firewall and shouldn’t be assumed to always function as one. A simple accept established, default drop firewall rule should do the trick and should be used on both v4 and v6 regardless of NAT (and probably is on your router already).

If your goal is privacy in the sense of blending in, you can still use NATv6 and this is a good use case for it. This is what VPNs like Mullvad use. If your goal is privacy in the sense of being more difficult to track across sessions, you can enable IPv6 privacy extensions which essentially generates a new IPv6 address for every connection your device makes. So in this sense it’s more private than IPv4

Or you could just… learn to use the modern internet that 60% of internet traffic uses? Not everyone has a dedicated IPv4 anymore, we are in the days of mobile networks and CGNAT. IPv4 exhaustion is here today.

Best to set a firewall rule with nftables to block non-vpn traffic from leaving (you should also do the save for IPv4 traffic to prevent leaks in case the tunnel disconnects)

https://www.phoronix.com/news/Ben-Skeggs-Joins-NVIDIA

I think this will change. Nvidia hired devs on Nouveau, NVK is coming along, etc

Some of it probably comes from other companies that are unable or unwilling to relicense it even if Nvidia wanted to

Looks like the birdie has escaped phoronix…

In the small chance that this comment is serious, Nvidia is found this because the corporate server-based customers need the ability to troubleshoot and debug the driver.

The actual trade secrets are being moved into the proprietary firmware blob and out of the driver.

PNG is a rather slow algorithm based on the DEFLATE compression from zip/gzip. You could extract to bmp or some other uncompressed format. First, to ensure it is lossless, make sure it supports the video’s pix_fmt without needing conversion.

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

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

Ratios that extreme would probably only be seen in cases where the source video was really poorly compressed anyway, which is what the commenter probably experienced. I’ve had that happen before too. Expect more like half the size compared to H264, which is still pretty good