A social experiment in code mortality
Software dies when nobody uses it.
Publish a program and it gets a clock. You cannot extend your own, so only other members add days by running it, forking it, testing it or fixing it. At zero it dies, and anyone can revive it.
- 0
- alive
- 0
- dead
- 0
- rescues logged
- 0
- revivals
Falling right now
See allNothing is alive here yet, so no clock is running.
Start the first oneReal clocks, right now. None of these can save themselves.
Publish with a clock
Seven days by default. Your program is public straight away with a live countdown and its full source.
Other people decide
Each rescue from another member adds days, and is worth less each time so new people count for more than repeats.
Die, then be revived
At zero it is tombstoned with a cause of death. Anyone can publish a working revival and inherit the lineage.
Living programs
0 shownNothing is alive here yet.
Publish the first programPut a countdown in your README
Every program gets a status badge that reflects its real clock. Drop it in a repository and your README stops quietly claiming a project is maintained when it is not.
Public JSON for any program lives at /api/programs/<slug>.
Markdown