Where it is up to
Churr is not finished, nobody has used it yet, and there is nothing to download.
built Passes automated tests
- The server: every one of its 325 API operations, the live connection, the operator commands, sign-in in all its forms, bots and webhooks, the Slack importer and the export
- Links between servers: shared channels, hubs, and moving a channel onto a hub. The hub and the push relay build and are tested
- The web pages (setup, sign-in, joining, account, admin) and the web chat
- The app, for text chat, forms, search, channels, settings and themes
- The sealed-chat encryption, in Go and in Dart, passing the same test vectors
being built Started, not done
- Calls, in the app and the web chat
- Sealed chats, in the app and the web chat
- Phone notifications
- The desktop tray icon
untried Never yet done
- A person using it end to end, or a real community on it
- Android, Windows and Linux builds of the app
- Real Apple and Google push
- Fetching a real certificate
- Building or starting the container image
- The 5,000-member load test
- Real Slack, Discord and GitHub payloads, and a real Slack export
- The reverse-proxy configurations
- An outside review of the sealed-chat encryption
"Tested" means automated tests that run in the project: server tests on SQLite and PostgreSQL, browser tests of the web pages, and tests of the app. Every run so far has been by hand, on one laptop.
A person sets the requirements and makes the decisions: the scope, the trade-offs, and every ruling where two parts of the design disagree. AI agents write the design documents, the code and its tests, and run them.
Churr uses no AI service when it runs.
When a group could reasonably try it. The source will go up at github.com/tikaydaes then, under the AGPL-3.0: if you run a changed version as a service, you offer its source to the people who use it.
There is no mailing list, because Churr does not do email. Watch the GitHub account, or come back.