It will certainly force users/providers/administrator to review their patching processes, and velocity.

Nah. It was Kash Patel.

But the contractor who created Clippy isn't.

Yes, but it involves Skynet, and a Terminator traveling back in time to kill Clippy.

There are still places without any cell service in the US. Unlike for landlines, the government does not mandate that cell service must be available at your address.

It does not work without a human prompt. It's a productivity tool. A very helpful one. Until you run out of quota on Anthropic. I have been alternating between Claude code on the $20 plan and Claude code with qwen3.6 locally. Much slower locally, but still faster than what I would be able to write and test alone without the tool.

Not for FDIC-insured funds.

Surely this is a loss-leader. Expect the rug to be pulled.

It was just a typo. I didn't even see it. Vision issues.

This is untrue. You can still get POTS lines here in California. It costs a ton. In some areas, there is no cell service, and it is a lifeline. IDSL was still offered to me as an option until recently.

I do have cable, though, and capped my POTS wiring.
i

Much of the Netscape code is still alive in Mozilla.

Amateur. ln is even faster.

I have been using this very model this week. It walks, not runs, on my 5950x with 64gb ram and 8gb 3060ti gpu. Takes a minimum of 3 mins to respond to any prompt. 10+ if it writes code and files. Results vary greatly. Often takes 10 prompts to fix a small bug. Which means hours. Claude can do it right, in minutes. And then i exceed the limit, and am stuck for the next 6+ hours. Or worse, a full week.

I have been using local AI. Claude code with qwen3.6. 10-20mins is typical wait time for a code change. It introduces 1 bug for each onw it fixes. Not a pleasant experience. When using the Claude Pro service, it is much faster and competent. And i blow my daily limit within 30 minutes. Neither is great.

My pfSsense Proxmox router VM has the DHCP & DNS server parts covered.

I'll look at adding containers for TFTP and NFS.

No PoE for me - there is no wiring for it. And I don't have any managed or POE switches. But I can force power cycle the Pis with Wifi smartplugs. All 3 of my Pis have their own already. So, that should handle reboots / updates.

My vision is failing to the point I can no longer read physical books. Inserting microSD cards is also a huge problem, as they are too small and I can't focus on them.

SD cards are still faster than my mesh Wifi in terms of raw throughput. Theoretically about 320 Mbps. My mesh Wifi peaks around 200 Mbps, I think.

My Pi 3B+ is actually not using the Wifi NIC. It's using the Ethernet NIC, and connected to a switch, with a Unifi AP acting as a Wifi bridge. So, I believe there is no technical obstacle to PXE booting. The Pi doesn't even know it's using Wifi.

I don't use an off the shelf NAS. I have a Proxmox box now running a whole bunch of services, including pfSense in a VM, Unifi network in a container, and of course Samba for file serving. Many more, too. What are the 4 services needed for PXE booting ? I would much prefer not to have to deal with SD cards again. Easier to replace a disk image on the server than an SD card when messing up. Especially reading/flashing the SD card for backup/restore purpose is very slow.

I have two other Pis 3B+ on my two Carrier HVAC systems using RS-485. I would also prefer if they could PXE boot. They are using the Wifi NIC, though, so I guess that wouldn't be possible. Maybe with an SD card and a bootloader doing Wifi connection only, then getting the rest of the OS over Wifi.