GitHub issues
Bugs, feature ideas, and questions go to the issue tracker. It is the primary channel for feedback and the clearest view of what is being worked on.
Community · get involved
Help build movement infrastructure.
This is infrastructure for movements to own — built in the open, for anyone to take part. Three real ways in today: file an issue, follow the build, or contribute code. The code lives at github.com/rabble/riot.
Right now
What exists today — and what does not.
No invented channels. This is the actual current state of how to engage with the project, so you can pick the one that works for you.
Follow the build
Updates post as each phase clears its gate. The home page tracks status; protest.net is the parent project for broader movement-tech context.
Read and run it
The whole repository is open source: most is MIT-licensed, while the riot-anchor and riot-anchor-protocol crates are AGPL-3.0-or-later. Clone it, build it, test it. See the open-source page for the layout and commands.
No chat room, no mailing list
There is no Matrix room, Discord, Slack, or mailing list yet. When one opens it will be announced here and on the issue tracker, not guessed at. Please don't trust a channel that isn't linked from this page.
Ways to help
Concrete contributions that move Riot forward.
Riot is a Rust core with native iOS/Android apps on top, plus a gateway and this static site. Help is welcome across all of it — and most valued where it matches the project's honest boundaries.
Report what breaks
The most useful first contribution is a clear issue: what you expected, what happened, and how to reproduce it. The app is a prototype, so rough edges are expected and finding them helps.
Work on the Rust core
Signing, storage, merge, and the protocol mapping are in the Rust workspace. The workflow is TDD with coverage thresholds — see AGENTS.md at the repo root, which applies to every contributor, human or agent.
Help with privacy and threat modeling
Encrypted groups are not shipped yet and will be reviewed under their own threat model before they are. People with experience in nearby-messaging, relay trust, and seizure resistance are especially welcome on those issues.
Make Riot useful to a real group
The point of Riot is communities that can keep publishing through a blackout. If you are part of a group that might use it, that use case — and what it needs — is a contribution in itself.
If you are not sure where to start, the issue tracker is the single best entry point. For how Riot compares to adjacent systems before contributing on the protocol side, start with the protocol field guide.