This page documents the current implementation of the entry keypad, and proposed additions. If you would like to help out, you might want to make this page more accurate, or implement some of the wishlist. This system is a delicate balance of different people's needs and concerns, so changing the basic way that it operates would be poor form. To build an alternative way to access Noiseridge, consider building software that accesses the API.
Please add yourself here if you're a stakeholder on this project.
A script on Minotaur called baron manages the payphone keypad stationed outside Noisebridge's gate. The payphone is connected to Minotaur by a long blue ethernet cable which runs up the stairwell and across the ceiling. When a use enters a valid code followed by #, baron uses the Noisebridge API to open the gate, while the payphone LED flashes blue, and a "happy" sound is heard. If an incorrect code is entered, or enough time passes between button presses, the payphone LED flashes red, and a "sad" sound is heard. If the gate API throws an error, the light turns red and a sad noise is played three times.
- The keypad hardware hooked up to Minotaur at /dev/ttyS3 https://www.noisebridge.net/pipermail/noisebridge-discuss/2012-February/028485.html
- /usr/local/share/baron/noisebridge-baron/baron.py - baron script, takes arguments --port=/dev/whatever and --codefile=/var/blablabla/codes
- /etc/init/baron.conf - jesse's init script
- /usr/local/share/baron/codes.txt - codes file, any line starting with a 4-7 digit number (ignoring whitespace) is interpreted as a valid code, # is used for comments
Please label your codes so that others know who to contact and when to expire them.
To improve, the code, please issue a pull request against https://github.com/noisebridge/noisebridge-baron. It you improve the hardware, please document the new state here, and make note of your changes in the changelog. If you would like to make changes to how the system works, as opposed to just how elegantly it's implemented, please talk to the people named above.
The software has to be gone over to make sure it can be run in multiple instances, because someday we will put a second keypad at the top of the stairs, so that buzzing someone in requires a code.
We should also create a web-accessible door-opener page which requires a code (from the same database) so that, in case we decide to end the uncredentialed door opener page, we will have a code-authorized alternative already in place.
There can be any number of plugins that generate keycodes, as long as they are non-destructively copied to the codes file on Minotaur.
- Add a "bad" codes list, to block codes from being reused.
- Add the ability to expire codes - maybe a comment in the codes.txt file?