734 karma · joined July 20, 2017
What I meant was that we do not need to go from the Wild West straight to “anyone who, as an individual, connects a `bad thing` to an LLM will go to jail”
Instead of what they are doing now, which appears to be actively courting as many of them as possible for vast sums of money.
the difference here is that they’re calling for someone to stop them, which is both weird and unconvincing because these immensely powerful billionaires can in fact make their own decisions
When people tell you who they are, you should believe them. These guys are all Yud acolytes who think they are the only ones who can prevent Roko’s Basilisk.
But how does automated AI code review help, here? Doesn’t it just reinforce that they don’t need to look at it (or change their habits), because the AI review will catch the issues?
Here’s GPT 6’s answer to the prompt “What macOS terminal apps support gestures? Include a reference to the docs on how to enable/configure them.”:
iTerm2 supports configurable three-finger taps and swipes for switching tabs/panes, creating splits, pasting, etc. Set them up under Settings > Pointer > Bindings. Check for conflicting macOS trackpad assignments. [1]
The others are more limited: Ghostty supports macOS lookup/Quick Look gestures [2], while WezTerm lets you bind scroll events—for example, Ctrl+scroll to change font size. [3] Neither is equivalent to iTerm2’s gesture bindings.
For custom gestures without switching terminals, BetterTouchTool can map app-specific trackpad gestures to the terminal’s existing keyboard shortcuts. [4]
[1] https://iterm2.com/documentation-preferences-pointer.html
[2] https://ghostty.org/docs/features#macos
[3] https://wezterm.org/config/mouse.html
[4] https://docs.folivora.ai/docs/trackpad-mouse/magic-mouse-tra...
My personal experience is that LLMs are quite good at one-shotting complex solutions in both Rust and Go, and tend to be idiomatic.
https://jacobin.com/2026/07/ai-nationalization-sanders-liber...
The single thing that seems to have helped is that we all agreed to use OpenSpec early on, and to commit the specs alongside the code.
I have no affiliation with OpenSpec and I don’t suspect it’s doing anything unique here, but having the intent develop alongside the code in the repository seems to have ensured that agents have a more holistic view of the project.
It’s a night/day difference when I use an agent against this codebase that integrates its changes using OpenSpec and those that ignore it.
When you see, “Wow, Fable is number one”, you might think it’s a good writer, but that’s not what the benchmark says.
I have no reason whatsoever to use this, but it's a cool project!
Obviously, 75% of Americans do not develop dementia. Do more who are overweight develop dementia than those who are not? Well...it's hard to say when 3/4ths of the population is overweight.
The watermark: counting instances of 'load-bearing seam', 'the hard truth', 'and that's the whole point'.
Hedonic adaptation prevents us from asking "is this worth the downsides, or should we go back to how it was?"
I don't think I understand why they aren't leveraging the increased speed to do batching to serve more customers at a "normal" tok/s.
Is the limitation, even on cerberus, still that the cache can only serve so many concurrent sessions over time? Is there no scaling advantage? I genuinely do not understand how any of this works.
Until, of course, it isn’t - but at that point, the budget is reallocated, there’s no funding, there’s simply nothing we can do except continue to pay this AI contract.
Vote with your wallet works when you’re talking about local businesses. It doesn’t work when the only factor that determines where the money goes is the executives signing the contracts.
Giving agents pointers to the right patterns, libraries and services helps avoid expensive grep goose chases, but if you're already curating the input you can do the same thing with small repositories.
Tools, especially open source ones (linters, static analysis, scanning, LSPs, IDEs, etc) are not built for monorepos, and with AI Agents working in the monorepo results in an enormous increase in input tokens as the agents are constantly trying to grep this giant source tree.
I'm sure it's possible that we're doing the monorepo thing wrong, but I'm genuinely curious what the upside is that you're experiencing? Or are these drawbacks unique to our implementation?