Skip to content
A social coding experiment that updates its own code democratically.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
cron merging PR #550: Re Reopen #443 according to #364 - Twitter Api Working Jun 11, 2017
data merging PR #468: Added imps to voting reactions Jun 2, 2017
dev merging PR #506: Make docker scripts current directory independent Jun 4, 2017
github_api merging PR #545: Fix "ci failed" issue v2 Jun 10, 2017
lib merging PR #497: Implementing the DB stuff Jun 5, 2017
server merging PR #532: Creating link to meritocracy page Jun 6, 2017
startup.d merging PR #515: Fully deprecate old web server and fix new one Jun 4, 2017
twitter_keys merging PR #550: Re Reopen #443 according to #364 - Twitter Api Working Jun 11, 2017
.editorconfig Add an .editorconfig May 23, 2017
.flake8 Fix flake8 errors and run flake8 in Travis May 27, 2017
.travis.yml merging PR #433: Add ESLint to lint JS files Jun 1, 2017 Only insignificant nitpicks May 26, 2017
description.txt Add homepage to the repo May 26, 2017 merging PR #533: A Declaration of the Independence of Cyberspace. Jun 6, 2017 merging PR #393: Migrations May 30, 2017 Fix flake8 errors and run flake8 in Travis May 27, 2017
requirements.txt merging PR #550: Re Reopen #443 according to #364 - Twitter Api Working Jun 11, 2017 merging PR #550: Re Reopen #443 according to #364 - Twitter Api Working Jun 11, 2017

NOTE: This repository is dead. See #559 for more information, including a V2.


Build Status Gitter chat ChaosBot Uptime Robot status

Chaos, the vacant and infinite space which existed according to the ancient cosmogonies previous to the creation of the world, and out of which the gods, men, and all things arose.

ChaosBot is a social coding experiment to see what happens when the absolute direction of a software project is turned over to the open source community.


How it works

  1. Fork the code and make any changes you wish. (see Development)
  2. Open a pull request.
  3. If there is general approval* from the community, the PR will be merged automatically by ChaosBot.
  4. ChaosBot will automatically update its own code with your changes and restart itself.
  5. Go to #1

A Declaration of the Independence of Cyberspace

We have freed ourselves from the chains and shackles of project admins and owners, diminishing our value to work for there needs. We are now making a fully equal community, where everyone has a equal say. (Please see

Join us.

How chaosbot works, in a gif

In effect, you get to change the basic purpose and functionality of ChaosBot, at your discretion.

What will ChaosBot do? It's up to you. The only thing it does now is update itself with your changes. And as long as the code connecting itself to new changes remains intact, ChaosBot will continue to grow and change according to your will.

Some things it could do

  • Provide some useful service to people.
  • Be malicious.
  • Recreate itself in a different programming language.
  • Break itself and die.

There is no set purpose. What ChaosBot makes itself into is entirely up to the imagination of the open source community.

Wondering how to contribute? Try implementing a feature requested here.


Votes on a PR are determined through following mechanism:

  • A comment that contains an emoji signifying a vote somewhere in the body counts as a vote for or against the PR.
  • Same for reactions on the PR itself
  • The PR itself counts as 👍 from the owner, unless they vote otherwise.
  • Voting goes on for the duration of the voting window - currently 2 or 3 hours, depending on the local server time.
  • While the voting process is going, users can change their reactions and edit their comments, effectively changing their vote.

Emoji which count as votes are:

  • +1: 👍 👍 ❤️ 💕 💙 💜 💚 💛 💗 💖 🎉 😍 😁 😀 😂 😆 😄 😃 😈 👌 🔥 🤘 🙌 💯 ✔️ ☑️ 🉑 ㊗️
  • -1: 👎 👎 😕 ⁉️ ✖️ 🚮 ⛔️ 😟 😦 👿 😧 😬 😰 😞 😩 😖 😢 😫 💔 💩 💩 💩 🖕 🙅 🙍




Death Counter

Chaosbot has died 16 times. This counter is incremented whenever the trunk breaks and the server must be restarted manually. Last broken by #309


Chaosbot has been ruled by:

  • Democracy
  • Anarchy with #48
  • Democracy, as the anarchy commit crashed the server and was reverted
  • @PlasmaPower with #138
  • Democracy, as PlasmaPower relinquished his control with #153
  • Direct democracy + meritocracy with #377

Server details

  • ChaosBot runs with Python 3.6.1 on Ubuntu 14.04 Trusty.
  • Its process is managed under supervisor. Avoid writing your own process-management tooling unless it is going to replace supervisor completely.
  • It has root access on its server. This means you are able to install packages and perform other privileged operations, provided you can initiate those changes through a pull request.
  • Its domain name is
  • It's hosted on a low-tier machine in the cloud. This means there aren't a ton of resources available to it: 2TB network transfer, 30GB storage, 2GB memory, and 1 CPU core. Try not to deliberately DoS it.
  • MySQL is installed locally.


Q: What happens if ChaosBot merges bad code and doesn't start again?

A: Errors can happen, and in the interest of keeping things interesting, ChaosBot will manually be restarted and the death counter will be incremented.

Q: What is "general approval" from the community?

A: Users must vote on your PR, through either a comment or reaction, or a accept/reject pull request review. See Voting.

In addition, a member of the meritocracy must approve the most recent commit of the PR with a review. A member of the meritocracy approving their own PR does not count. The meritocracy is determined by combining the top 10 contributors and the top 10 voters. The current meritocracy can be viewed here.

Q: What if ChaosBot has a problem that can't be solved by a PR?

A: Please open a project issue and a real live human will take a look at it.

You can’t perform that action at this time.