What's this about?
A librarian published a practical guide to turning off AI features across common apps and services. The thread was less about technique than exhaustion.
What exactly is the lock-in concern?
The immediate objection is unwanted features. The deeper one is architectural: when a company builds AI into a product's core rather than adding it beside the existing path, the non-AI path can quietly disappear. The example that landed hardest is Apple CarPlay reportedly requiring Siri to be enabled — if the AI feature is a dependency rather than an addition, "turn it off" stops being an option and the guide's whole premise erodes.
What's the community saying?
HN 265 points, 163 comments
- "Companies forcing features nobody wants, that are also expensive to operate." The top comment's puzzle: this isn't cheap to run, which makes the push harder to explain as pure product logic.
- "Nobody asked for AI slop." The blunt version, widely echoed, with irritation at the burden landing on users to block, disable, unsubscribe and mitigate.
- The CarPlay discovery. The concrete instance of the lock-in fear — no fallback state, so disabling the assistant disables things that have nothing to do with it.
- The simplest strategy. "I immediately go 'fuck it, I'm not using that product' — I'm remarkably free of any intrusive AI." Extreme, and several people said it's the only thing that has worked.
- A practical request. Put the guide in a repository so changes can be tracked and corrections submitted — treating the list as living infrastructure rather than a blog post.