Prototype, built in the open
Every day, people make a community through meals, meetings, stories, decisions, celebrations, care, and shared work. Riot helps them publish what they know, decide together, coordinate what needs doing, and carry their collective memory.
Ordinary life, made together
It is the kitchen after a long meeting. A garden workday. A block party, repair table, local paper, childcare rota, needs-and-offers board, and the argument that becomes a decision. It is people making culture, care, memory, and useful things together.
Riot does not create trust or solidarity. It gives people adaptable public tools for practicing, recording, and carrying the work that already makes a community real.
Grounded in the field
Riot's design is not built on guesses about what communities need. The prosocial-local-spaces literature — three independent studies of real communities — converges on a structural answer Riot's architecture reflects. Riot is in a different lineage (activism, shutdowns, mutual aid) but the lessons transfer.
Front Porch Forum ships finite "issues," not a stream; 63% of members read every one. Its survey of 13,473 members found forums that were more active were rated less favorably — the platform people value is the one they don't live inside. Riot's sync model carries community tools, not a feed to scroll.
The 2025 "Local Connection Crisis" survey (2,028 people across urban, suburban, and rural communities) measured a real effect: belonging scores rise when users can name their steward by memory. Trust comes from people, not algorithms. Riot's moderation is a lens applied by humans the community knows, not invisible ranking.
The top reasons people abandon local spaces — toxicity, spam, notification overload — are symptoms of the engagement-extraction model. Riot has no server pushing a feed and no algorithm optimizing for time-on-device. The "Nourish" and "Take a Breath" signals from the 14 Civic Signals framework are satisfied by transport design, not moderation labor.
Riot is not Roundabout and is not trying to be. It shares the structural lessons — bounded, human-moderated, non-extractive — from a different center of gravity: activism, internet shutdowns, and degraded connectivity. Read the full synthesis ↗
Four human verbs
The status labels describe today's software, not the social practice. Communities have always done these things.
Share signed public updates and community media: dispatches, local knowledge, corrections, photos, and stories.
Available in the prototypeKeep meeting artifacts, polls, discussion, decisions, and a shared record. Riot supports the work around a meeting; it is not live audio or video.
Available in the prototypeUse the bundled checklist, supply board, roll call, and quick poll. Broader schedules and locally adapted workflows remain direction.
Available in the prototypeKeep already-held community state and installed tools useful on a functioning device, with different paths for exchange and reach.
Use builds capacity
A tool used for a festival rota, cooperative decision, neighborhood publication, community meal, or repair day becomes familiar. People learn where knowledge lives, how decisions are recorded, and how to correct one another. When conditions become difficult, that shared practice already exists.
Disruption is harmful; it is not the fantasy. The hopeful subject is what people already know how to build together.
A bounded mechanism
Participants can hold community data instead of only accessing a service. Signed records let Riot verify that a record came from a particular key—not that it is true. Already-held data and installed tools can remain locally useful on a functioning device.
Bundle files, QR-assisted references, nearby exchange, public gateways, and anchors offer different paths with different status. Hosts can improve reach and discovery without becoming the sole authority for identity or the only holder of community history.
This reduces dependence on one provider; it does not promise total independence or a complete reachable copy.
Read the detailed trust and transport model in the protocol field guide.
A community should be able to leave a provider without leaving one another.
Direction, not shipped
Public by purpose
Current public Newswires are places for publishing and collaboration. Posts are intended to be read, copied, and carried.
Private encrypted groups are a separate future direction, not part of today's prototype. For a private conversation today, use a purpose-built private messenger such as Signal.
Read Riot's short privacy boundary or the technical details.
Participation, not purchase
Try Riot with a real community. Adapt a tool. Bring a publication, meeting, meal, festival, or shared project. Tell us where the software gets in the way, and help practice the future together.
Intellectual lineage. This page is informed by Rebecca Solnit's A Paradise Built in Hell, which attends to the solidarity and civic possibility people often make together amid disruption. That work does not endorse Riot; it helps name a human capacity worth building for. Read the publisher's description.