silotis

This is just a variation on the broken window fallacy. There are any number of engineering projects one could embark on that would stimulate R&D and provide a productive output in their own right.

I have a regular exercise routine I do every day. Believe it or not some people still have insomnia even when they follow all the usual lifestyle advise.

Eh, I've found my insomnia to be largely independent of the amount of exercise I get. I can run 5 km during the day and still only manage 3-4 hours the next night.

The situation with H.264 is complicated by the fact that it refers to a whole series of standards released over an extended period. The vast majority of H.264 videos in the wild only use the High profile which was first published in March of 2005, therefor any claim of essential patents covering these videos with an expiration date after March 2025 is dubious.

MPEG-LA tries to create FUD around this by lumping all H.264 patents into one big pool and never clarifying which edition of the standard a patent applies to. The end result is that anyone not already ignoring MPEG-LA's patents is unlikely to start until _all_ of the patents in MPEG-LA's H.264 pool have expired which is still several years out.

CalFAIR is subsidized in the sense that insurance companies are forced to pay into it. Insurers of course pass this cost on to their customers. Combined with price controls on insurance this is just taxation with extra steps.

With DNSSEC + DANE Brazil would not have needed to make any deal with MS to be able to issue certs for .br domains and they would not have been able to issue a cert for google.com.

Admittedly DNSSEC has issues to put it mildly, but it does serve as a counterexample to your claim.

The article gives examples of CEOs borrowing against their shares. The article provides no examples of CEOs rolling those loans over until their death.

This isn't about getting free internet, no competent ISP will let the link come up without a serial number registered with the port. This is about bypassing the awful gateway hardware many fiber ISPs mandate.

IME most new residential fiber deployments in the US are using XGS-PON which provides 10 Gbps in both directions. Typically ISPs don't put the maximum number of clients in a node that the standard allows. I've heard 32 is a common number in practice.

Obviously it'd still be a bad idea to run a high traffic server on a residential connection, but as long as you're not streaming 4K video 24/7 or something you'll probably be OK.

If you're fortunate enough to have the older BGW210 you can bypass it without specialized hardware by having your router proxy the authentication requests.

https://pyther.net/2020/05/03/bypass-att-gateway-openwrt.htm...

It's a good point in general, but in this case it's not clear if the cost of re-writing the existing codebase is less than the cost of staying with a memory-unsafe language.

We know from past experience that it takes an extreme amount of time and effort to harden a browser written in C++ against malicious web content. The Ladybird codebase is not particularly "old" in any sense of the word. Judging by Github's stats most of the code is less than 4 years old and it is still a long ways from being ready for general use. I think it's safe to say Ladybird still has a vast amount of work to be done fixing vulnerabilities that arise from lack of memory safety.

I find it quite plausible that the cost of re-writing the existing code in Rust is less than the cost of fixing all of the current and future bugs in the C++ codebase that Rust would catch at compile time.

Bittorrent normally hash checks all content against metadata in the torrent file so a simple MITM wouldn't be enough to inject malicious data unless the torrent metadata itself is being sent in the clear.

> does not switch to 200MHz for a minute during video calls

I had a Dell work laptop that did the same thing. As far as I was able to tell the system had a bug/fault that continuously asserted the CPU's BD PROCHOT line when the integrated webcam was active. I don't think it was an Intel bug, the CPU was just responding to the external signal that (falsely) indicated the system was overheating.

When Social Security was first passed into law it was sold to the public as a sort of compulsory annuity, not a means of mass wealth redistribution.

Artillery has been the number one cause of combat casualties since World War I. The tech is obviously changing, but soldiers dying out of sight of the enemy is not new.

The trick is to enforce conformance right from the start in the first implementation of a format. Shipping a product that doesn't interop with the existing tools is a non-starter so the devs will have to fix their shit first.

As you say, unfortunately the genie cannot be put back in the bottle for formats that already have defective implementations in the wild.

This isn't limited to the US. For the trip distances we're talking about here European trains are often just as expensive as flying if not more so.

From a legalistic standpoint it makes sense: the FAA spends a lot of resources regulating SpaceX's activity, therefor tax SpaceX to pay for it.

From an economic and geopolitical standpoint it's clearly a poor choice to introduce an extra tax on something which drives a large amount of economic activity and is an important strategic asset.

The relevant statute[0] says that companies are required to notify the EPA before they start manufacturing new chemicals. So knowingly hiding a new chemical from the EPA would be a risky play, if the government found out the company (and more importantly the people involved) would presumably be in deep shit.

https://www.law.cornell.edu/uscode/text/15/2604

Almost. I tested this a few years ago and IIRC zstd at its highest settings is typically about 5% larger than LZMA. So there is a difference, but probably not enough for most people to care.

It was less "I might be killed" and more "my son/husband might be killed".

To be fair I think the conservative objection is not quite that filing taxes needs to be annoying. The concern is more that automated tax calculation makes it easier for people to be blissfully unaware of how much of their money is going to taxes. Even now most people have minimal awareness of their tax burden thanks to automated tax withholding.

That's not how it works on modern CPUs. Power draw at "100%" utilization can vary widely depending on what part of the core is being utilized. The SIMD units are typically the most power hungry part of the CPU by a large margin so just because a job finishes in less time doesn't mean total energy is necessarily lower.

According to the pdf the source isn't even pure peanut butter. It also contains sugar and vegetable oils so it's probably based on one of the cheap emulsified varieties.

The cheap old varieties of insulin are still available and still cheap. What's expensive are the newer analogues which make it much easier for diabetics to manage their insulin levels.

Cloudflare's lack of EDNS doesn't prevent DNS based routing. It can still be done based on the DNS request's source address. This will be the IP of the Cloudflare POP closest to the client.

Lack of EDNS only makes DNS based routing slightly worse if your CDN has a POP density similar-or-greater-than Cloudflare's.

> assuming a network size of ~25k DHT Server nodes

I guess they've given up on the idea of end users running full nodes.

There still might be some value in having a federated CDN service, but I think they will struggle to compete with centralized CDNs for all the same reasons other federated services have struggled.

DHTs have had support for mutable pointers for a long time. The bittorrent DHT has BEP44 which was published in 2014.

http://bittorrent.org/beps/bep_0044.html

The average user doesn't have the level of visibility into the system to know that the middlebox is the one causing the problem. Instead whatever changed last gets the blame, regardless of what's actually at fault. So if a user's existing applications set the spin bit "correctly" and a new application does not, the new application will be judged as buggy, not the middlebox which has been working fine until now.

It's also possible for a state to suborn a registrar to publish a fraudulent record so that the state can get a DV cert issued by the CA of its choosing. This leaves the WebPKI in no better shape than DNSSEC + CT when it comes to state level attackers obtaining fraudulent certifications.