There is a particular anger that shows up when someone buys a machine, the vendor cloud shrugs, and the physical object becomes e-waste while still mechanically fine.
Unlocking a deactivated Cricut Maker sits in that genre. Craft hardware. Creative tools. A device that should have been scissors with a motor. Instead it is a subscription to permission.
I care about this beyond hobby cutters. The same pattern is spreading through routers, printers, tractors, medical accessories, and home batteries. Purchase becomes a revocable license. Repair becomes a gray art. Secondary markets get poisoned because buyers cannot know whether the object will still obey them next year.
The product promise and the control plane diverge
Hardware marketing still sells permanence. Buy this. Own this. Make things in your house.
Then the control plane ships elsewhere. Activation servers. Account binding. Firmware that phones home. Features gated on cloud moods. When the vendor changes strategy, your bench tool inherits the strategy.
Engineers understand why companies do it. Fraud. Consumables revenue. Support boundaries. IP theater. Ecosystem lock-in dressed as "experience."
Users understand something simpler: a machine that refuses to run without a remote blessing is not fully theirs.
Those two understandings are now in open conflict.
E-waste is an engineering outcome
We talk about sustainability as materials science and recycling policy. Fine. Also look at software decisions that brick working devices.
A locked cutter in a closet is not abstract. It is metal, electronics, packaging, shipping carbon, and a person who now needs another unit. Multiply that by product categories and you get a quiet industrial leak. Not a headline oil spill. A thousand small discards justified by terms of service.
Right-to-repair fights often sound legalistic because they have to. Underneath them is an engineering ethics question: should physical usefulness be separable from vendor continuity?
I think yes. Not because vendors owe eternal free cloud services. Because basic local function should degrade gracefully when accounts die, startups pivot, or regions lose support.
What good ownership looks like in practice
I do not need every device to be fully open. I do need a minimum bar:
- core function works offline after legitimate purchase,
- repair documentation exists for wear parts,
- account deletion does not corpse the hardware,
- security updates are separable from engagement metrics,
- and secondary buyers can reset and use the device without a morality play.
If a business model cannot survive that bar, it may be a rental business pretending to be retail. Rentals are fine when labeled. The dark pattern is selling "yours" while retaining a kill switch.
Why hackers keep unlocking things
People reverse these systems for the same reason they always have: the object is right there, the restriction feels illegitimate, and competence is a form of dignity.
I am glad that competence exists. I wish it were less necessary.
Every unlock writeup is both a celebration of curiosity and an indictment of design. Celebrate the curiosity. Fix the design.
If you build devices, ask an ugly question early: what happens to this product when our company is gone, bored, or acquired by someone who hates the legacy SKU?
If the honest answer is "it becomes sculpture," you did not ship a tool. You shipped a timed souvenir.
I have started applying that question to my own side projects when they touch hardware or local-only workflows. If a feature requires my personal server to stay alive forever, it is not a feature. It is a future apology. Shipping a local fallback is less glamorous than a cloud dashboard. It is also how you respect the person who trusted you with money and shelf space.
Ownership should be dull. You paid. It works. You can maintain it. The cloud can add delight without holding the motor hostage.
Anything less and we are just decorating landfills with DRM.
Top comments (0)