“Any time someone puts a lock on something that belongs to you and won’t give you the key, that lock isn’t there for your benefit.”
Cory Doctorow offered this line in his book Information Doesn’t Want to Be Free. Doctorow used the principle while explaining digital locks, copyright enforcement, and the power of intermediaries over creators and audiences. A technical restriction can prevent copying, but it can also prevent repair, migration, accessibility, research, or continued use of something a customer believes they own. Its force comes from consequences the speaker had already seen in working systems and institutions.
Control over the key reveals whose interests the system protects. If only a vendor can authorize ordinary use, ownership becomes conditional on that vendor’s continued permission, service, and business model. The insight is therefore less about admiration than about where to direct engineering attention. In practice, that means asking what changed, who gained new capability, which assumption carries the most risk, and how the result would be checked by someone who did not share the builder’s expectations. It also means comparing the claimed benefit with the maintenance, access, and recovery work required to keep it real over time. The quotation earns its place by sharpening those questions instead of closing them.
Security controls and access permissions can protect users, organizations, and creators. The quotation targets unilateral restrictions on owners, not every lock. The test is whether the affected person has meaningful authority, notice, portability, and recourse. Nuance matters because slogans can scale faster than the safeguards and assumptions that once surrounded them. Strong technology reporting must preserve this boundary, because the same words can support very different choices after the original constraints disappear. Readers should be able to see both the useful principle and the evidence that would require a different judgment. A responsible reading separates the speaker’s documented claim from broader promises that admirers may attach to it later.
Connected devices, subscriptions, and cloud accounts make purchased products dependent on remote policy. Doctorow’s rule encourages buyers and designers to ask whether a lock prevents harm or merely preserves leverage after the sale. Its modern value lies in making accountability part of technical quality instead of an afterthought. Teams can make that test concrete through review, accessible documentation, independent feedback, and measures that include failures as well as successes. The same discipline should follow the system after launch, when real users reveal consequences no prototype fully predicted in advance. Those habits turn a memorable insight into work that readers, builders, and institutions can examine and improve.
Cory Doctorow offered this line in his book Information Doesn’t Want to Be Free. Doctorow used the principle while explaining digital locks, copyright enforcement, and the power of intermediaries over creators and audiences. A technical restriction can prevent copying, but it can also prevent repair, migration, accessibility, research, or continued use of something a customer believes they own. Its force comes from consequences the speaker had already seen in working systems and institutions.
The source record connects the wording to his book Information Doesn’t Want to Be Free, which is the context used for this post.
Control over the key reveals whose interests the system protects. If only a vendor can authorize ordinary use, ownership becomes conditional on that vendor’s continued permission, service, and business model. The insight is therefore less about admiration than about where to direct engineering attention. In practice, that means asking what changed, who gained new capability, which assumption carries the most risk, and how the result would be checked by someone who did not share the builder’s expectations. It also means comparing the claimed benefit with the maintenance, access, and recovery work required to keep it real over time. The quotation earns its place by sharpening those questions instead of closing them.
The interpretation focuses on a decision or design principle that readers can test against actual systems.
Security controls and access permissions can protect users, organizations, and creators. The quotation targets unilateral restrictions on owners, not every lock. The test is whether the affected person has meaningful authority, notice, portability, and recourse. Nuance matters because slogans can scale faster than the safeguards and assumptions that once surrounded them. Strong technology reporting must preserve this boundary, because the same words can support very different choices after the original constraints disappear. Readers should be able to see both the useful principle and the evidence that would require a different judgment. A responsible reading separates the speaker’s documented claim from broader promises that admirers may attach to it later.
Connected devices, subscriptions, and cloud accounts make purchased products dependent on remote policy. Doctorow’s rule encourages buyers and designers to ask whether a lock prevents harm or merely preserves leverage after the sale. Its modern value lies in making accountability part of technical quality instead of an afterthought. Teams can make that test concrete through review, accessible documentation, independent feedback, and measures that include failures as well as successes. The same discipline should follow the system after launch, when real users reveal consequences no prototype fully predicted in advance. Those habits turn a memorable insight into work that readers, builders, and institutions can examine and improve.
Explore more "Quotes of The Day"
Discover more notable quotes from influential voices across politics, science, business, technology, sports, and culture. Each quote offers insight into how ideas, beliefs, and decisions shape the world around us.