Infrastructure should be

  • Embedded: Infrastructure is “sunk” into, inside of, other structures, social arrangements and technologies
  • Transparent: Infrastructure is transparent to use, in the sense that it does not have to be reinvented each time or assembled for each task, but invisibly supports those tasks.
  • Reach/scope: This may be either spatial or temporal — infrastructure has reach beyond a single event or one-site practice. Occurs across multiple places.
  • Learned: Strangers and outsiders encounter infrastructure as a target object to be learned about. New participants acquire a naturalized familiarity with its objects as they become members.
  • Links with conventions of practices: Infrastructure both shapes and is shaped by the conventions of a community of practice (e.g. the QWERTY keyboard).

Source: Steps Toward an Ecology of Infrastructure: Design and Access for Large Information Spaces by Susan Leigh Star and Karen Ruhleder


“A platform is when the economic value of everybody that uses it exceeds the value of the company that creates it. then it’s a platform”

What is infrastructure even?

Which came first, the infrastructure or the applications that depend on it?

See also: Myth of the Infrastructure Phase

“infrastructure as potential energy held in suspension” (Boyer)

Do we need to define infrastructure?

Thus, infrastructure design requires a more subtle approach: creating the right incentives, environments, and dependencies to encourage well-being while preserving user autonomy.

Infrastructure can be emergent:

“I have admiringly called this the “Procrastination Principle,” wherein an elegant network design would not be unduly complicated by attempts to solve every possible problem that one could imagine materializing in the future. We see the principle at work in Wikipedia, where the initial pitch for it would seem preposterous: ‘We can generate a consummately thorough and mostly reliable encyclopedia by allowing anyone in the world to create a new page and anyone else in the world to drop by and revise it.‘”

Hard and soft infrastructure

Hard infrastructure refers to hard rules and goods (e.g. parks, laws, highways, etc.)

Soft infrastructure is upheld as a social protocol, an institution whose maintenance relies on dedication and value alignment. More closely related to social contracts


To oblivion and beyond: Imagining infrastructure after collapse

An alternate take on creation vs maintenance

Infrastructures do not function forever. Like everything else, they lose in the universe’s constant battle against entropy.

As Boyer (2016) argues, infrastructures possess a temporal persistence that “points deathward.” Oil refineries along the Texas Gulf Coast, for example, take part in a system of resource extraction that hastens climate change; at the same time, climate change threatens the continued functioning of these refineries, and oil companies have requested federal funds to protect their facilities from the destructive environmental phenomena that they have a hand in creating (Associated Press, 2018).

  • Cruel optimism: the experience of placing hope in an object that perpetually prevents the realization of that hope
  • Angry optimism: “does not attempt to escape or control the dangers of the present or to return to the comforts of the past but instead looks forward to the possibilities of a time beyond these”

Not just maintenance, but rebuilding. In the context of infrastructure and collapse, cruel optimism is the belief that rebuilding is a way to heal. “Breakdown might instead represent an opportunity to create futures that do not resemble the past.”

Lifetime of an infrastructure doesn’t just cover its functional lifespan. Many components to this:

  1. Service life (assuming ongoing maintenance, duration of functionality)
    1. Risk analysis and modelling is one way of calculating thius
  2. Material life (how long will it take for the material of the infrastructure itself to degrade and erode)

In fact, for the vast majority of infrastructures, the material life of an infrastructure will far outlast its service life (e.g. concrete aqueducts of the Romans almost 2000 years ago).

Repair, they argue, is just an excuse for returning things to what they used to be rather than see it as a chance for change. Berlant’s worry is that the repair of infrastructure merely reinstates a comfortable yet crisis producing past

A new form of utopianism in science fiction: “if present conditions lead inexorably to collapse, how can that collapse be used as a resource from which to build more equitable ways of life”


The commons: Infrastructures for troubling times

The common usually refers to an orientation toward life and value unbound by concepts and divisions of property, and points to the world both as a finite resource that is running out and an inexhaustible fund of human consciousness or creativity

Sensus communis: “‘common sense’ is merely the bourgeois order of truth standing in for the universal, what Stoler calls ‘‘a folk epistemology.’’”



How do we draw the line between an end product and infrastructure? How should infrastructure regulate usage on its platform (if at all)? Been thinking about AWS’s decision to remove Parler recently and whether it was warranted for AWS to do so. At what level of infrastructure should something become a ’public good’? As more and more of our digital infrastructure is built out under private companies, does it change how we govern content on top of it?