Elinor ๐ฑ
Community shift coordination that lives where your community already talks โ Telegram โ and stores everything on an open protocol โ Nostr.
Named after Elinor Ostrom, who showed that communities can govern shared resources themselves โ with clear boundaries, rules people shape together, and transparency instead of permissions.
How it works
- Sign up in one tap โ the day's shifts live in a pinned group message and a Telegram Mini App; every change is announced publicly in the group.
- Anyone can fix the schedule โ add or remove anyone; the guardrail is attribution, not permissions.
- Your agenda stays current โ subscribe once to a personal or community calendar feed (Apple/Google/any ICS app).
- Reminders that recruit โ public per-shift reminders mention the crew and carry an "I'll take it" button while spots remain.
- Open by design โ everything is standard NIP-52 events on a public Nostr relay. Any client or agent can read the schedule or sign someone up: see the protocol docs.
For developers & agents
The documentation describes the relay, the two event kinds (31923 shift occurrences, 31925 signups), the exact filters to read the schedule, and the rules for publishing signups. Agent-readable versions: /docs.md and /llms.txt.