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.

I'm not seeing a paywall on the site. uBlock Origin must be doing something.

The UHF app on our Apple TVs & iOS devices and the UHF Server in Docker to act as a PVR gives us everything for a few $ a month paid in crypto.
We haven't had cable since ~1999-2000. Downloading and the *arrs have kept us happy, but the better half wanted to check out some live sports. So IPTV it was.

One of our guys said something to the effect of "Copilot is Corporate Chat. It knows all the useless filler of management-speak, but lacks the competence of the people in the trenches.

Ouch.

I've used Claude at home for ages. Work was wanting to get some AI stuff for us and the only 'blessed' one is CoPilot. Everything else it blocked. All senior management seems to know about AI is "Hurrr... Copilot and ChatGPT."

Out team of ~8 (pentestesting & VA) were unanimous about Copilot being crap and Claude being the top dog. So some higher ups OK'd a Claude Teams package for work. To bypass the CorpSec tards, we use it from our lab environment that has its own unmonitored link and IP range.

Anthropic/Claude is just so far ahead of OpenAI/ChatGPT and MS/Copilot it's not funny.

Please don't use the word "smear" in the comments on this post. Thank you.

Just get rid of clock changes altogether, and set the time in reference to UTC and time zone without any "daylight savings" type adjustment. Each of the 24 time zones (-12 to +12) should be one hour off from it's neighbors, and should be straight (time doesn't care about state lines).

There also should be no half hour off zones. If that matters that much, just use UTC and forget about time zones altogether.

Hashes would be perfect for this. Take the ID number, hash it, store the hash. If you need to verify, hash the ID number and compare it to the recorded one. Still no need to store _anything_ like an ID.

Also, don't hire third party companies to do it. They won't get it right. They never have. They never will. After all, it's not _them_ on the line if there is a breach. Somehow the third parties always seem to slip past the blame and liability and it all goes to the ones who hire them.

Even my Raspberry Pi has PCIE now. Why would the cripple a general purpose CPU by not giving it a bus that can keep up with it?

That was pretty much my point. Everything about it was so vague that it was, essentially, meaningless. There was no who (as you point out), no what, no where, no when, no information on which action could be taken. An example of what I, personally, would prefer is:

"You and I should connect tomorrow, I'll send an invitation based on our calendars, and work out the requirements and a plan to meet them."

So... you would like to communicate at some time using some method, but not a meeting, to work out the details of some thing which may or may not be a task and determine who will be putting what work into meeting the requirements that are still to be defined as part of this communication.

In other words, let's get together later and figure everything out.

What I don't understand is why there is no card/slot for M.2 drives. Even a full length one is not much larger than a USB drive, and the slot could be made similar to a larger USB-C style connector. Is there something technological, like trace length limitations, that makes that difficult?

I ran a dedupe on my drive and eliminated 8 redundant copies of the goatse guy.

#SaveWaterWithGoatse