Ownership vs licensing: bricked products and rented access
New York announced a game ownership bill that would require ownership rather than licensing. A top comment said they used to think offline modes and community servers were too expensive for developers, and no longer do. Meanwhile a custom server revives Neato robot vacuums, with the author explaining Generation 3 robots need nip.io workarounds. Legal experts warned that Meta's new terms still grant broad scraping permissions, and commenters said never to rely on robots.txt. The Anthropic thread on blocking Claude Code subscriptions from using OpenClaw fits the same frame: users feel they paid for capacity and the vendor redefined what they bought.
The pattern: people are tired of products where the vendor can change the rules or kill the service. Reverse-engineered servers and legislation are the two responses.
The nuance is cost. Supporting shutdown modes is real work, and a subscription that allows unlimited third-party harnesses is a real strain. Neither side's case is fake.
So what?
If you sell hardware or connected software, plan an end-of-life story now: a local mode, open protocol, or released server code. If you build on a vendor's subscription, treat third-party access as revocable.
Read these
NY announces game ownership bill requiring ownership rather than licensing
Custom server to revive neato bots
Legal experts warn Meta's new terms still grant broad scraping permissions
Tell HN: Anthropic no longer allowing Claude Code subscriptions to use OpenClaw