..."Okay. We've got a bipolar topic here I see"
No. There is no bi-polarity. And the people booing you are not mentally ill.
The students hate that you think it's the greatest new thing.
And they love the time it did not exist.

To use a much overused term where it's actually appropriate:
When you try to convince people their view is invalid and they are mentally ill (bipolar), you are not merely disagreeing with them; you are gaslighting them.

people. Just spray a little Ubik on it and it'll be all better.

Mythbusters did an experiment to disprove this. I'd say they are about as credible as these researchers. https://www.youtube.com/watch?...

At a large US auto manufacturer our crew were responsible for commissioning controls systems and maintaining the drawings related thereto.
The HDDs on the CAD machines were simply NOT big enough to contain all the drawings so we had stacks of ZIP disks and both mobile (SCSI by parallel port) and internal (SCSI) readers for them.
One of the more experienced guys bought a CD burner (that was a $600.00 purchase at the time) and would make weekly backups for us. Blank CDs were $10.00 apiece at the time.
A couple of years into it we started hearing the "click of death". Thank you Butch; you saved our work!

To me the hoops that smoothbrains will jump through to avoid IPv6 and stay on legacy IPv4, especially when hosting, is pathetic. NAT, port forwarding, tunnels, blah blah blah blah.

I have something like ~1.2 trillion times the number of routable addresses that the entire IPv4 space has. Not all are reachable, of course, just the services that need incoming access and they're each on their own isolated DMZ.

Forgot to add: if you enable IPv6, be sure to use the browser extension IPvFoo. It shows a small 4 or 6 in your URI bar to let you know what protocol you're connecting to. Once enabled, you'll see just how much stuff out there actually is IPv6.

Started the move about 18 months ago when I decided to get off my lazy ass. My ISP gives out a /56 prefix, so that lets me run 256 /64 subnets/VLANs in the house, currently there are ~10 in use. Everything get a GUA through SLAAC and I use RAs (Router Advertisements) to give ULAs to everything. Any external facing services get their own VLAN and /64 for the system(s) as needed. Firewall blocks all incoming as they usually do by default and I punch a hole for the external-facing systems. They can't reach back into the network, they only answer the phone. All the systems update DNS dynamically if the prefix or full address ever change.

I have an SSH bastion set up. In all this time there has not been a single SSH attempt from the internet. On IPv4 it was constant background noice.
For those legacy IPv4-only systems on the internet, I set up NAT64. I have an IoT VLAN and IoT 2.4 GHz wireless network that are only IPv4 because a lot of IoT network stacks are junk.

I'm still farting around with it, but man oh man, there's no way I'd go back to IPv4. It was one of the best moves I've done in ages.

Increasing UDP throughput simply by inlining a function is a big deal!

And nothing of value was lost.

Or would that just be a firehose?
Who watches the watchers?

Sadly while your logic sounds spot on, the reality is, that TV still does ACR (basically hashing each screen sometimes multiple times a second) and builds one hell of an accurate profile of everything you watch. Even if the source is HDMI. And it's still sold.

Food for thought, that HDMI cable to your dedicated device, it likely supports networking, so the TV has a path to the internet even if you don't connect an ethernet cable directly to it, or add in your wifi creds.

I've heard of traffic 'accidents' where a diabetic went hypoglycemic, passed out, and drove into other cars, pedestrians, etc. For some reason the news always reports it as a 'medical event', but the point is, people are killed by diabetics due to their diabetes way too often. It is an apt analogy. An idiot decides to drink and drive an puts people at risk. An idiot with diabetes fails to control their blood sugar and decides to drive, putting people at risk.

Yeah, it's easy to add more code to fix stuff that should be deleted. Just have the launcher code call your new code which bypasses all the old code. The old code can happily remain, it'll just never be called. No special skills required. If you look at the windows codebase, you'll see this technique everywhere.

Triggered or flamebait?
Hard to tell says Poe.
Either way you are dragged kicking and screaming into the present.

Welcome, friend.

Do not feed the troll.