Kerbonut

This is the exact reason why the Apple Vision Pro is failing, because they put a toy OS on it instead of an actual operating system that is conducive for getting real work done.

Can you standardize with all of your tools on a common registry key and settings paradigm and same plugin/skills paradigm and common method for enterprise delivery? It’s a pain in the neck getting all of this set up and deployed throughout the org.

A fellow pyanodons player I see

They most likely truck in the brine from a mixing facility to reclaim the oil and truck out the brine to disposal when refilling the oil stock.

They look like above ground pits. Empties are showing the white paint and ones with brine look dark.

Wire typically means internet connection, and it’s hardly the bottleneck

Tailscale Aperture is having trouble doing the OAUth2 connection. Can you support oauth2_dcr or test with Aperture?

Claude Code is not the model, it's the harness. You can use any model you want with Claude Code to varying degrees of success. I use Qwen3.6-27b daily with Claude Code as an example.

> put a temperature sensor on the oscillator

At that point, couldn't we just use the temperature value to compensate for the drift?

Wouldn't a temperature compensating algorithm be just as effective?

Wrong. They disable it because it’s a safety thing. They still count it towards their metrics that FSD was enabled.

It’s still counted as FSD enabled. Would you prefer FSD to remain active and potentially cause further collateral damage after an accident causing who knows what kind of damage to the vehicle? Safer to shut it down when systems are working and brace for impact. Seriously use your brain.

That's like Joe Pesci in My Cousin Vinny where he stays overnight in a cabin and wakes up and freaks out at every little noise, but when he's held in contempt and there's a prison riot going on, he's sleeping like a baby.

I built my own tooling around templated manifest files (jinja2) and management via ansible playbooks (templated).