ABOUT THIS WEIRD LITTLE THING

DESIGN NOTES

why a snorse?

It started as a way to give a Signal group a few shared utilities without giving everyone another app to manage.

quick when called, back in the shell when finished.

Signal is already the room

People already talk there. A bot can live at the edge without asking everyone to install another app or remember another password.

boring is a feature

SQLite. Explicit scopes. Read-only calendars. Small commands. Durable volumes. Manual upgrades. Technology chosen to be understandable and recoverable.

capacity should be honest

The public host does not pretend to be infinitely elastic. It measures itself, pauses admission safely, preserves existing groups, and shows aggregate status.

exit doors matter

The shared version is convenient; self-hosting gives a group more control. Both use the same application and state contract.

the name

A snorse has the speed to show up when called and a shell to disappear into when the job is done. That is about as deep as the naming process got, but it also describes how the bot behaves.

The gray and olive pixel-art snorse mascot
move thoughtfully; carry your state with you