Over 90% of my family's connections are from our home, but most of the rest is from our data plan, so it's three more IP addresses plus when I'm at my job.

They do that, I'll complain.

Who knows if I won't sue for mal practice.

Way back then, when GPLv3 was veing written, this scenario was already had in consideration. We needed stronger copyleft for the online world of cloud services, and that was something Affero GPL and GPLv3 addressed.

But all the "business savvy" open source advocates made it hard to reach a consensus (they did not want the closure of the loopholes), instead they caused a bit of FUD chaos and then proceeded to have a strong impulse of new cloud oriented software that went all the way opposite the GPLv3 and in fact opened MORE loopholes, hence the strong investment into MIT, Apache 2, and other less strong free software licenses.

This way, they could make proprietary versions (and many companies went the proprietary relicensing bait and switch model of "open core") or turn software proprietary for all practical effects by having it used in cloud services (without the additional requisites addressed by GPLv3) without a "download me" recourse.

Nothing good ever comes from "there's a problem, instead of fixing it let's add more complexity".

And adding contracts to free software... IMHO, is an epitome of that.

People who root their devices may use RCS and ensure they use real E2Em instead of one app that probably is spoofable and tappable...

So No RCS for you! (think Soup-Nazi guy voice)

The goal is quite clear at the end of the page, and it's one of replacing the GNU GPL (sort of like a constitution) with a license that allows the commons to be reduced.

"uutils is licensed under the MIT License - see the LICENSE file for details
GNU Coreutils is licensed under the GPL 3.0 or later."

Many browsers reside behind http proxies. Unless they are also using DoH and assuming that is not blocked for some fascist-like reason or another, you'd basically be crippling the browsing experience.

DNS is not really a good solution for this, but (stapled) OCSP might be, even if not without it's flaws).

I worked at AOL for 4 years. Layoffs happened every year like clockwork around the holiday season. Great people, shitty company.

Actually, Red Hat's RPM usage included gpg signing of each of the packages individually since before 2000 :)

I've been in court when I've seen judges reduce the fine based on speedometer calibration report from a mechanic.

US law used to recognize Mens Rae (guilty mind) as a necessary component for a criminal conviction. However, the War On Drugs has given rise to the predominance of strict liability in criminal law (whereas it was formerly confined primarily to civil law).

Grammatical mistakes, like disagreement in plurality or using the wrong word, are very annoying.

Insurance is one of the most tightly regulated industries around. It also has one of the most effective lobbying organizations around. This results in a lot of regulation that works on their favor, but it's by no means universal.

Why do I suspect more thought has been given to giving the bill a catchy acronym than has been given to the legislation itself?

Anyone who's worked for a company that uses the Mongolian Hoarde technique of software development can tell you that "not enough Indians" (literally) isn't the problem.

The whole point of the Thompson hack is that it would survive a source code audit. If you compiled the clean source for the compiler with a dirty compiler, it would insert the backdoor into the new executable, making it self-replicating in an virtually undetectable fashion. The code you compiled yourself would be byte-for-byte identical with the bootstrap compiler.