I want to see Google's HIPAA disclosure document for their Google Health app. If it does not clearly spell out that any PHI stored in the app is contained in the app and will not, as required under HIPAA, be shared within Google for other uses, or sold out of Google entirely, then it will be a warm day in Niflheim before they see me using their product.

And because the meta for YouTube is to pump out as many videos as possible, so that a channel owner has more 'content' for YouTube to be jamming ads into, from which the channel owner gets a sliver of payback from, there is a constant drive to push new videos out as fast as possible, so anything that slows down publishing new videos gets kicked to the wayside. The channels that use AI narration just push the script through an AI-driven text-to-speech system, and don't care whether it's using the right pronunciation for heterophones (i.e., talking about the bow of a ship and pronouncing it like the 'bow' of 'bow and arrow', when they could go back and tweak the script to have 'bough' instead of 'bow' to force a particular pronunciation, but that's additional work and time), and then just accept YouTube's default captioning because that's easier and faster; adding captions manually would slow down their pushing out slop even further.

So we should apply this maxim whenever we see someone parroting "The science is settled" declaration about climate change?

As I posted above, 100kWh of battery charging in 7 minutes requires a delivery of more than 850kW of power to the car. A home circuit rated for 100A at 220V is 22kW, 1/38 the needed power, so the 7 minute charge becomes almost four and a half hours at home, assuming that you have nothing else drawing power.

Edit: Left in the 'k' on the power delivery. 850,000W or 850kW, not 850,000kW. Some things just slip by checking.

If you assume a 100kWh battery, charging it in 7 minutes means that your one charging station has to deliver more than 850,000kW of power to your car. Good luck finding a charging site with megawatt-scale power delivery, and even more luck finding one that isn't splitting that power delivery among eight or sixteen charging stations.

It's all about the visuals. In a Zoom meeting, you can't be seen to be 'actively concerned' about climate change, so you're not going to get the publicity that having reporters photograph you displaying your deep concern about the climate and working to hammer out an agreement to phase out fossil fuels that will wind up honored more in its abrogation than its compliance. From the article: "But the real difference from half a century ago is that fossil fuel alternatives are ready for prime time." -- as Spain clearly demonstrated on 28 April 2025, when wind and solar was supplying 71% of the produced power, and a 5-second interruption caused tripouts across the Iberian peninsula and southern France, resulting in a total power outage lasting ten hours or more.

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.

Or force them to keep their constellations lower, which means the satellites have to carry more fuel to fight drag, but if they fail they'll just deorbit in a few years. You can go a bit lower and use air-breathing ion thrusters as well, and those will deorbit even faster.

The big danger is the stuff in higher orbits that takes 100-1000 years to come down.

I mean, a small online bookstore pivoted to become one of the most foundational structural elements of the internet.

Meh, sounds like a charge of Arson would be warranted, but not Attempted Murder.

Well, Hell, *I* can clone OSS in seconds via a pull. Jeebus. AI blah blah blah AI staff cuts blah blah blah paradigm shift....yawn.

Thank you, Baby Jesus.