Infrastructure on emsenn.net

Compute Infrastructure for Small Organizations

Fri, 03 Apr 2026 00:00:00 +0000

A small organization building a software system faces an infrastructure question that larger organizations can defer to specialized teams: where does the system run? The answer determines cost, operational burden, scaling path, and the degree of control the organization retains over its own systems. This text surveys the real options as of 2026, with documented pricing and practitioner-reported tradeoffs.

¶Virtual private servers

A virtual private server (VPS) is a virtual machine rented from a hosting provider, accessed via SSH, with full root control. It is the most common starting point for small teams.

Communications Infrastructure in Emergent Disaster Response

Sun, 08 Mar 2026 00:00:00 +0000

Emergent disaster response depends on communications infrastructure just as much as it depends on food, medicine, and volunteers. Communication channels, message relays, hub updates, and social-media routing are part of the material infrastructure that makes decentralized coordination possible [@ambinder2013; @kendrawachtendorf2006sensemaking].

¶Live information flows

The HSSAI report on Occupy Sandy shows that one of the network’s main strengths was its ability to identify needs and route information in near real time [@ambinder2013]. This is not just communication in the abstract. It is a practical infrastructure for moving people, supplies, and attention.

Dual Power and Survival Infrastructure in Emergent Disaster Response

Sun, 08 Mar 2026 00:00:00 +0000

One explicit current within emergent disaster response treats disaster relief as part of building alternative infrastructure. In this current, food distribution, clinics, wellness spaces, popular education, and energy systems are not only temporary emergency measures. They are part of a dual power strategy of building capacities people can continue to use beyond the immediate crisis [@madrabout2025; @madrprograms2024].

¶Survival infrastructure

Mutual Aid Disaster Relief’s language of survival programs makes this current explicit. Immediate aid is linked to long-term power, consciousness, and community capacity rather than being treated as neutral service [@madrprograms2024]. This is one of the clearest ways that disaster response becomes a site of institution building.

Warehouse

Sun, 08 Mar 2026 00:00:00 +0000

A warehouse is a storage and coordination site where incoming goods are received, sorted, held, and redistributed during disaster response [@wachtendorf2010; @watters2014].

Within emergent disaster response, the term matters because donated and converged materials become useful only if there is a place where they can be made legible and movable. Warehouses are therefore not merely storage containers. They are operational sites where classification, prioritization, and routing occur.

A warehouse can be temporary, improvised, or embedded inside a larger mutual aid hub. What defines it is its function in the logistics chain, not whether it looks like a formal facility.

Warehousing and Resource Cataloging in Emergent Disaster Response

Sun, 08 Mar 2026 00:00:00 +0000

Emergent disaster response often has to improvise logistics infrastructure quickly. Among the most important pieces are temporary warehouses and the practices of resource cataloging that make stored goods retrievable, interpretable, and movable [@wachtendorf2010; @nelan2016].

¶Storage as an active practice

Wachtendorf and coauthors show that large-scale disaster response is not only challenged by scarcity. It is also challenged by acquisition, reception, storage, and distribution problems created by material convergence [@wachtendorf2010]. Storage therefore is not passive. It is part of the labor of turning donations into usable support.

Dead Zone

Tue, 03 Mar 2026 00:00:00 +0000

A dead zone is a term emsenn introduces within the standardization as counterinsurgency framework to describe the end state of the domestication trajectory. It names an infrastructure that is standardized, maintained, and institutionally visible — but that no longer serves as a site of innovation for either insurgent movements or dominant platforms.

¶Characteristics

A dead zone infrastructure exhibits four properties simultaneously:

High legibility. It’s documented, standardized, and incorporated into reference architectures and regulatory frameworks. Institutions can “see” it.

Domestication Paradox

Tue, 03 Mar 2026 00:00:00 +0000

The Domestication Paradox is a concept emsenn develops within the standardization as counterinsurgency framework. It names a specific structural irony: the process of making an insurgent infrastructure legible and safe for corporate adoption also undermines the social and cultural energies that would have made adoption worthwhile.

¶The mechanism

Domestication reshapes an insurgent infrastructure in three ways:

Tightening interfaces — clarifying and narrowing what counts as “compliant” behavior, reducing space for divergent interpretations.
Decontextualizing goals — recasting the infrastructure as a general-purpose tool (“a protocol for interoperable social activities”) rather than an instrument of a specific political project.
Repositioning control — shifting de facto authority over interpretation and evolution from grassroots communities to standard editors, major implementers, and corporate participants.

From the corporate perspective, domestication looks attractive: the infrastructure becomes easier to integrate, explain to policymakers, and incorporate into compliance narratives. It reduces uncertainty and coordination costs.

Insurgent Infrastructure

Tue, 03 Mar 2026 00:00:00 +0000

Insurgent infrastructure is a term emsenn introduces within the standardization as counterinsurgency framework to name a specific kind of technical system: one that emerges from communities seeking to change the conditions imposed by existing platforms.

An infrastructure is insurgent when it scores high on generativity, autonomy support, and movement value, while its legibility and corporate extractable value are low or uncertain. Insurgent infrastructures are often messy, evolving, and embedded in local practices. Their meaning is tied to their role in a broader political and social project — building alternatives, resisting enclosure, or experimenting with new governance forms.

Standardization as Counterinsurgency

Tue, 03 Mar 2026 00:00:00 +0000

Standardization as counterinsurgency (SaC) is a framework emsenn develops to describe how standards bodies interact with insurgent infrastructures — technical systems that originate as challenges to the dominant platform order. The framework draws on James C. Scott’s work on legibility and state-building, and on analyses of protocol as a form of soft power.

The central claim: when a standards body engages with an insurgent infrastructure, the institutional logic of standardization — consensus-seeking, scope management, stakeholder alignment — tends to transform the infrastructure in ways that increase its legibility to dominant institutions while eroding its generativity, autonomy support, and movement value. This isn’t necessarily intentional. It’s a structural effect of the incentives and constraints that shape standards processes.