In computing, the robustness principle is a design guideline for software that states: "be conservative in what you do, be liberal in what you accept from others". It is often reworded as: "be conservative in what you send, be liberal in what you accept". The principle is also known as Postel's law, after Jon Postel, who used the wording in an early specification of TCP.

ike Jungius, Boyle made use of loose folio sheets that he called memorials or adversaria; yet he did not worry too much about a system of self-referential relationships that enabled intentional knowl-edge retrieval. When he realized that he was no longer able to get his bearings in an ocean of paper slips, he looked for a way out, testing several devices, such as colored strings or labels made of letters and numeral codes. Unfortunately, it was too late. As Richard Yeo clearly noted, ‘this failure to develop an effective indexing system resulted from years of trusting in memory in tandem with notes’.69

Simply put: alias docker=podman.

Follow this link to the Hypothesis extension in the Chrome Web Store. If this is your first time adding extensions from the Chrome store in Edge, click “Allow extensions from other stores”.

Fukuyama's work, which draws on both competition analysis and an assessment of threats to democracy, joins a growing body of proposals that also includes Mike Masnick's "protocols not platforms," Cory Doctorow's "adversarial interoperability," my own "Magic APIs," and Twitter CEO Jack Dorsey's "algorithmic choice."

The Gopher story is a perfect case history for Adversarial Interoperability. The pre-Gopher information landscape was dominated by companies, departments, and individuals who were disinterested in giving users control over their own computing experience and who viewed computing as something that took place in a shared lab space, not in your home or dorm room. Rather than pursuing an argument with these self-appointed Lords of Computing, the Gopher team simply went around them, interconnecting to their services without asking for permission. They didn't take data they weren't supposed to have—but they did make it much easier for the services' nominal users to actually access them.

Today's Web giants want us to believe that they and they alone are suited to take us to wherever we end up next. Having used Adversarial Interoperability as a ladder to attain their rarefied heights, they now use laws to kick the ladder away and prevent the next Microcomputer Center or Tim Berners-Lee from doing to them what the Web did to Gopher, and what Gopher did to mainframes.

this project uses adversarial interoperability, rather than rely on industry self-regulation or buy-in from fundamentally opposed stakeholders (browsers, advertisers, publishers)