The basic idea is that users rank the candidates (stream ideas) according to which they would rather watch, and an election is run before each stream to determine the topic of the stream. Since ranked choice voting lets users specify multiple preferences, this process can then be repeated for the next stream, where it will go to each user's second preferred candidate, etc.
This implementation is not written to be secure or efficient. Quite to the contrary. Users identify with a self-chosen username, and all that is required to change their ballot in the future (e.g., to add votes for new stream ideas) is that same username. This means that any user can change any other user's ballot simply by giving their username. So don't use this for anything serious.
To deploy, run:
$ sqlite3 db/db.sqlite < schema.sql $ cargo run --release
The web interface will now be available on port
To add new candidates for voting, use
sqlite3 db/db.sqlite and issue
insert statements of the following form:
INSERT INTO items (title, body) VALUES ("My Great Idea", "Here's why it's great");
To mark a candidate as no longer available (e.g., because a stream has already been produced for it), just mark it as done with:
UPDATE items SET done = true WHERE id = ?;
? is the ID of the candidate, which you can find with
SELECT id, title FROM items WHERE done = false;