pnw

The OP was asking about providers that have banned Gen AI. Fastly is definitely not that provider.

Interested to learn more about the Missileer device listed on the site...

How would we know such a society is possible? There's zero proof of that to date. Errors and inevitable catastrophes are part of the cost of a highly complex technically advanced society run by humans.

Yes, I read this report and came to the same conclusion. What did they expect when they opened Youtube for example? Also, there was no implication that the ATA transmitted was any different than what you'd see in a regular browser e.g. the automotive companies aren't sending additional data when you open Youtube in your car.

They are serviceable in the sense that you simply replace them when they fail. Given that they cost so little now and have a service life of decades, it's more cost effective than a traditional fixture. Older fixtures with LEDs jammed into them were always an interim solution, and more prone to failure simply because of the design.

I spent the weekend trying Deepseek 4 Pro on a Linux porting project and it led me down a complete rabbit hole where Linux wouldn't even boot by the end of the weekend. Waste of $120. Switched back to GPT 6 on Monday and Linux is booting again and I'm making progress.

The only thing I've found Deepseek and Kimi good for are security tasks that GPT refuses to do.

This is a summary of what Deepseek did and got wrong:

Lost the proven baseline: changed kernel source, configuration, compiler, RAM geometry, MMC width, and peripherals together. Matching an upstream commit did not preserve local boot fixes, making failures difficult to isolate. Misidentified an image: a file labelled “r18-known-good” actually contained the r23 parent bootloader. Filename-based reasoning replaced verification of the artifact’s identity and provenance. Shipped inconsistent boot contracts: flash-16b’s loader read too few kernel blocks. Fresh2 changed the device tree without updating the loader’s expected length and CRC, creating deterministic rejection before normal Linux handoff. Patched binaries without maintaining reproducible source: loader constants diverged from source, a separately compiled cache-flush length remained stale, and assembly used an oversized stage-two slot. Their causal contribution to hangs was not established. Overstated diagnosis: claimed failures were definitively in U-Boot, blamed compiler or IPU changes without controlled isolation, converted noisy observations into confirmed hangs, and neglected persistent journals as an alternative explanation. Mistook compilation for integration: framebuffer registration was incomplete, timing success handling was inverted, BT.656 selection was unreachable, encoder overrides were missing, and audio lacked software clock configuration. Misread hardware evidence: asserted interrupt-free PMIC operation, assigned RF to the wrong SPI controller, confused regulator identifiers with register addresses, and described repeated encoder writes as unique registers. Overclaimed results: treated kernel/probe indications as userspace success, presented earlier discoveries as new progress, and omitted failed flashing attempts from the final narrative.

I enjoyed this article because I've lived this story before and it's bemusing to be on the wrong side of a vendors distribution strategy.

But it was the "Steve from Dell" revelation at the end that absolutely killed me!

Seattle's push to add additional regulation, compliance, fees and inspections has resulted in an exodus of small landlords, which are down anywhere from 19% to 22% in four years depending on how you slice it, and an explosion in large landlords which are up 77% in the same period.

The city has basically consolidated the rental market so it works best for large corporations. Was that the intent?