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

Fair enough. I've definitely done an A/B setup manually for significant upgrades, and it has saved me a lot of headaches. I don't see anything that indicates whether root would be available out of the box; that is a wait and see. I would expect the display system to be Wayland, so nothing magical there.

Access to both Flatpak and Snap would leave a wide selection of OSS available. I'm not a fan of either in their current form, I've run into too many issues with both - mostly due to assumptions made by the packager about permissions or environment. I use KDE as my primary DE, but I still prefer a proper package manager over their Discover store.

What I don't like, and it is part of the reason I left Microsoft behind, is the lack of control over my system. I imagine that I am not part of the target audience for this, though, as my "daily drive" is an off-road adventure.

So KDE wants to get in on the walled garden money that Apple and Google are already dominating. I have enough problems with Flatpaks not running properly on distro where I can go in and patch the issues that this is a complete non-starter for me.

If that is the case, then it can best be summarized as "Nice code you've got there. Would be a shame if someone injected a trojan. For a suitable 'donation' we can make sure that doesn't happen. We're not responsible for anything that happens if you don't pay your dues."

It's just another walled garden that developers will have to pay to enter, and consumers will have to pay to use. (And I have full confidence that Google will find a way to make both ends pay.)