The Free Software Movement was a line in the sand. In the 80s and 90s, as the industry was rushing to lock software behind proprietary licenses and call that progress, a handful of people steered a cultural movement with the goal to prevent this at any cost. Decades later, the results are in: ostensibly total victory in infrastructure norms. Open source is now the default way software is built. Almost all students learn development through it, and no CIO at any institution today needs to justify the decision to build on open source, and it has become so deeply normalised.

If we look closely at what we won, every one of the four freedoms is a freedom over a thing you can hold - Run the program, study and adapt it, share it, improve and release it. But, software itself never existed in isolation, and this is especially true with every passing year. You can run free software end to end, every line auditable, every license clean, and it changes almost nothing about your actual position, because the restricted protocols beneath them, the opaque hardware that it runs on, the service it talks to, the platform that authenticates you, the API that can change its terms overnight, are all places where these freedoms are have been routed around. In fact, the irony hiding in plain sight is that GitHub: the social layer built around Git, where most open source projects live, is itself a closed system, where many of these freedoms are meaningfully constrained, and where the rules can change overnight. Moreover, the actors arriving at this layer are no longer just companies optimizing a subscription, they are Governments who are moving to wrap the whole stack inside national priorities. The lesson they learnt is simple: You don’t need to own the code if you own the layer the code runs on. If this kills the four freedoms, will the entire edifice collapse? Did the free software movement lose the long game?

This talk argues that the four freedoms secured freedom, but they do not secure freedom over the systems that software increasingly depends on. You can run entirely free software while still relying on infrastructure whose rules can be changed without your consent. The missing freedom is therefore a freedom from dependence on any single actor controlling the infrastructure beneath it. Call it the fifth freedom: the guarantee that the systems we rely on remain neutral and legible to all, applying the same rules regardless of who you are. Achieving that requires more than open source licenses. It requires systems engineered for credible neutrality, where no participant can permanently capture the commons. Yet those guarantees ultimately depend on the communities that defend them. Neutral protocols need communities willing to resist their capture, and communities need neutral protocols that cannot quietly be bent to private interests. Together, they form the technical and social foundations of infrastructure that remains trustworthy over time.

Speakers:

Shyam Sridhar: Ethereum Foundation

Shyam Sridhar leads the Academic Secretariat at the Ethereum Foundation, serving as the interface between the Ethereum research ecosystem and academia by connecting open research questions with scholars and supporting independent research.