Everything it does
Each one carries a tag. built means it is in the code and passes automated tests. being built means work has started. Nothing here has been used by a real community yet.
Channels
Public and private, grouped into sections the admin sets and each person can fold.
Sub-channels
A channel can hold channels of its own, indented under it. No tree lines.
Chats
Between any set of people, without making a channel first.
Threads
Replies stay with the message they answer. A thread that outgrows its channel can be moved out into one of its own.
Slow mode and locks
For the channel that needs a breather.
Retention that deletes
Set a period and older messages are removed, not hidden.
Safe Markdown
Headings, lists, tables, code with highlighting. Nothing in a message can run a script or load a remote picture.
Edits with history
Edits and deletions keep their history until it is purged.
Files
Served only as downloads, from the server's own address.
Reactions, pins, bookmarks
And custom emoji, if the admin allows it.
Search
Everything you can read and nothing you can't, with filters for place, person, date and files.
Link previews
Off unless the admin turns them on, because fetching a page tells that site your server's address.
Polls and forms
Named or anonymous, with live results. A form builder for anything longer than a poll.
Checklists
Tick boxes in a message that anyone in the channel can tick, with who ticked and when.
Reminders and scheduled messages
Write it now, send it later.
Saved replies
For the answer you give every week.
Bots
A bot is an ordinary account with a token. It posts cards with fields, pictures and colours.
Webhooks
Accept Churr's own payloads, and Slack's, Discord's and GitHub's. Only hand-made payloads have been tried so far.
Passkeys
No passwords and no email addresses. Recovery codes for when a device is lost.
Company sign-in
OIDC or SAML, if your group has an identity provider.
Second factor
An authenticator app or a second passkey, where an admin requires it.
Invites
People join by invite. Nobody can sign up to your server unless you let them.
Sealed chats
End-to-end encrypted, between exactly two people. The encryption is written and tested; the screens for it are being built. It has not had an outside review.
Calls
Voice, video and screen sharing, carried by your own server.
Phone notifications
Through a relay that learns which phone to wake and nothing about why.
Shared channels
A channel shared between two Churr servers, linked directly. Tested, never used for real.
Hubs
A hub carries channels between many servers. It cannot read them: servers encrypt to each other first.
One program
A single Go binary with its database inside. No configuration file.
SQLite or PostgreSQL
SQLite by default, and a command that moves a community between the two.
Backup while running
One command writes a complete, consistent copy of the data folder.
A way in, and a way out
An importer for Slack exports, and an export of everything the server holds. No real Slack export has been tried yet.
Moderation
Time-outs, bans, a word filter, reports and an audit log.
Admin console
People, groups, channels, sign-in, outside connections and themes, in the browser.
Web chat
Served by your server. Works at phone width.
Phone and desktop apps
One codebase for Android, iPhone, macOS, Windows and Linux. Text chat works in it; it has not yet been built for Android, Windows or Linux.
Themes
Dark, light and a high-distinction palette. Make your own, share it as a link, and Churr checks it is readable.
Not out yet. Nearly a thing.
There is nothing to download today. The status page says exactly what is built, what is being built and what has never been tried, and it is updated as that changes.