I've moved remote to https://s.mcquay.me/hackerbots/ and stood up routes for go
get on the hackerbots repos. I had to update the imports for this to take
effect.

See golang.org/s/go14subrepo for background.

This was done to make cross-compiling work again

also updated config file

including a fix for using pointers instead of values.

did this to allow for other configs in our namespace.

http://talks.golang.org/2013/bestpractices.slide#25

Removed unused global

The bug here was that when you would try to start a game it would still be nil
after the block where g was redefined. Just me being sloppy.

Added some debugging

Create new bserv binary

Herein lie the following ideas:

- change package visibility of many things
- try to stash the globals into structs
- the code is far from correct; it merely compiles

This finalizes the work on getting the server to support multiple encodings for
players and spectators.

Typically client offers supported encodings, then the server chooses the
optimal one.

This is the first step involved in letting go clients talk gob to the game
server.

Still missing: actually use the client's prefered encoding

I just realized that there is no need to pass around a slice to something to
which protoTalker already has access.

I could never remember the url, so I print it out now.

unfortunately there is an issue with how these are calculated, and they don't
decrease as things quiet down. Well, the bad numbers are their for your
consumption, and should Just Work TM when appropriate changes in
bitbucket.org/smcquay/bandwith land. And they will. But I'm tired now.