Developing Open Source Software is a Political Act

The core claim is that software—especially proprietary, cloud-based, and subscription-driven software—functions like a political system because it reliably enforces rules, shapes what people can do, and can quietly lock away parts of identity and decision-making. That matters because modern life increasingly depends on these systems for memory, communication, visibility, and even basic social participation; when the “rules of the game” are controlled by companies, users lose democratic leverage.

A philosophical starting point becomes a practical one: the “extended mind” idea argues that cognition isn’t confined to the brain. External tools can become part of how people think and remember. The transcript illustrates this with everyday examples—looking up an address versus recalling it, or using a notebook as “spare memory” in Alzheimer’s. It then pushes the analogy into the digital era: keyboards, cloud storage, smartphones, and online services act like external memory systems. But this reliance creates a new vulnerability. If the coupling between a person and the tool is disrupted—no reception, a stolen or inaccessible notebook, a cloud outage—core cognition and daily functioning degrade.

That fragility becomes an argument for why software development is political. Reliability used to be a reason to trust computers; now complexity and interdependence create “chain dependencies” across operating systems, internet connections, cloud providers, and developers. A concrete example is Cloudflare’s load balancing: it routes traffic through its infrastructure and can keep popular sites online, yet even a small bug can make major services inaccessible for hours. The transcript links this to broader systemic risks: cloud outages, vendor lock-in, and the way subscription models shift power to companies that can cut access—citing Adobe’s 2019 Creative Cloud disruption in Venezuela after U.S. export sanctions.

Beyond outages and pricing, the transcript argues that proprietary formats and hidden source code create a form of captivity. When file formats are proprietary and export options are controlled by vendors, switching becomes difficult. Even when companies offer “read-only” tools after subscriptions end, users effectively accept ongoing control over their own data. The same logic extends to platforms like YouTube, Facebook, and Twitter, which present themselves as neutral “platforms” while monetizing user data and shaping visibility—making protests and activism more dependent on online reach.

Finally, the transcript ties software to governance and checks-and-balances. Unlike laws that can be debated and interpreted by courts, software rules are enforced automatically at the lowest level. That removes ambiguity but also removes democratic contestation: users can’t vote on features, and developers can change behavior unilaterally. Functions embedded in software—such as form validation—can constrain identity categories and choices without any “political” label.

The proposed remedy is open source. Public source code enables scrutiny, community oversight, and easier data migration through machine-readable formats. The transcript frames open source as a way to reintroduce transparency and accountability into the “outsourced mind” of modern computing—turning software into a political arena where users can demand changes through public issues and collective review.