Code

Architecture Overview

SCHI.SM uses Mumble in TCP-only mode over Tor using a SOCKS5 proxy to create a means of location-anonymity through Tor's onion routing. The server is a standard Mumble server, while the client will be a custom, command-line implementation of Mumble which will launch every time the communicator device is booted up.

TODO

• Add TCP-only mode and SOCKS5 support to mumble-ruby
• Create a command-line based Mumble client on top of mumble-ruby which interfaces with the GPIO pins of whatever hardware platform is picked so that push-to-talk and channel switching within a server can be done with physical buttons
• Tie in some sort of text-to-speech system (festival?) to notify the user when certain things happen (user joins channel, battery low(?), etc.

THOUGHTS

So mumble-ruby already implements TCP-only as described in the mumble protocol spec, wherein UDP packets are simply thrown in their entirety right into the TCP stream. That should be fine for us, and it also means that we can just use the gem as it comes.

I would imagine the application running on the device as being a background service that maintains a connection to the mumble server and listens for button presses and such. CLI would be effective as a POC, but what we really want is a daemon.