Open source
Source code can be inspected, modified, and shared under its license.
Field guide
What would cultural infrastructure look like if communities could understand, operate, shape, and leave the systems they depend on?
A short manifesto
Centralized services can be extremely useful. The question is what capabilities communities might want to retain alongside them.
A useful service can still concentrate control over discovery, moderation, pricing, and access. Communities may want options they can operate or leave.
Event pages, posts, recordings, and relationships can disappear when an account closes or a provider changes direction. Portable records make cultural memory more durable.
Sometimes. The real question includes labor, cost, maintenance, accessibility, governance, and succession—not only whether software can be installed.
Interoperable formats, owned domains, exports, feeds, and clear account boundaries make an exit possible even when hosted services are convenient today.
Capability, consent, understandable operation, repair, memory, and meaningful governance may matter more than maximum engagement.
Vocabulary
Open source, federation, decentralization, and community ownership overlap, but none automatically guarantees the others.
Source code can be inspected, modified, and shared under its license.
An individual or organization operates the service infrastructure.
Independent services communicate through shared protocols.
Control or operation is distributed across multiple parts of a system.
Different tools can exchange information and work together.
Data or identity can move without being rebuilt from scratch.
Participants connect directly or share responsibilities without one central service path.
The local copy and local interaction remain primary, with networking added around them.
A community has meaningful control over operation, decisions, responsibility, and succession.
Community ownership is a governance question, not merely a network topology.
Navigate by intent
The field guide compares models and tradeoffs without asking you to learn every protocol first.
Offline and local networks
Compare a phone-only Bluetooth approach with dedicated low-power LoRa radio networks.