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.

Even when residential and office/retail type businesses pay flat rate, heavy industrial electricity users pay based on time of day. When there's high demand, they can even be cut off (in exchange for getting lower rates the rest of the time). Being able to buffer electricity use allows them to cut costs.

Both ran without preceding ads. At both, just before the films started, I was thinking the theaters were awfully empty. Then, about 20 minutes in, people started coming in.

It's not scifi at all.

They hit the Earth's atmosphere at just below escape velocity (they were going 11.024 km/s, escape velocity is 11.186 km/s). If you do that at an angle that is too shallow, you skip off the atmosphere and enter an elliptical orbit. They intentionally did one skip to bleed off some energy, to give them a more precise entry to the landing zone.

LOL outsource it to the same SpaceX who's repeated failure to meet targets and obligations are the reason Artemis III won't be landing on the Moon? SpaceX was contracted to supply the lander and is so far behind they have no idea when (or if) they will, so NASA has re-opened the competition and is trying to get Blue Origin back in the game.

Well, aside from anything else... coming down way off target wasn't really much of a possibility. They were either going to splash down on/very near target, or not at all. The reentry corridor coming from the Moon is extremely narrow, and missing it long or short would not result in a splashdown (either bounce off the atmosphere or burn up), and similar for heat shield or parachute issues.

...My installation of minidlna still works fine, is Free Software, and doesn't phone home or exfiltrate my metadata.

Again, it's about power saving. Idle 1000BASE-T draws noticeably more power than idle 100BASE-TX (IIRC the drop from 100BASE-TX to 10BASE-T is not as significant). There are Energy Star ratings and EU rules about how much power an "off" and "standby" device can draw, so dropping to a lower NIC speed helps reach those levels.

There was a proposal for a "low power idle" mode extension of 1000BASE-T, not sure if that went anywhere or got implemented.

My $DAYJOB's data center switch upgrade got switches that have 48x 10G SFP+ ports plus 8x 100G QSFP+ ports. When we installed them, we realized that some really old Dell Poweredge servers try to drop to 100M when using shared DRAC (with the dedicated DRAC port also being 10/100M only), and the switches don't support 100M. We also had to look at a bunch of rack PDUs to find options that were 1G rather than 10/100M.

100M uses less power than 1G, so I guess that's why Dell did that (sounded like a good idea to some engineer), and probably PDUs are using ancient embedded chips that only do 10/100M. Supporting 10/100M adds complexity to the switch port PHY that isn't commonly used in DCs, but it's still an annoyance for us.

Grok was constantly say it was doing something that it had ZERO ability to, and I kept calling it out and it kept apologizing and then immediately doing it again.

As a guy who spend 5 figures a year on Ai, the last thing I want is that. I know Claude and ChatGPT also do it, but Grok was doing it CONSTANTLY.

Aaak. I think it was. That'll teach me to work off of decade old memories...

Well, it probably won't teach me.

Given that the Roberts Court is one of the most corporate-friendly in history, this decision comes as something of a surprise.

Nonetheless, it appears to be largely concordant with the so-called "Betamax case" from the early 1980's which established the principle of significant non-infringing uses as a defense and, despite passage of the DMCA, still largely informs the contours of contributory infringement.