Client updates managed by 'updates' service.

I eventually want both the news and connection info to come through this
way, and I'd like the server to take over the update looping again to
further reduce the back-and-forth communication.

Off-topic, but I should also improve the chat registration experience,
and add AngularUI.
Split FetchCtrl into many other controllers; other big changes.

There's also a 'states' service to manage state between the controllers.

And a 'conversion' one to handle LTc exchange rates.

The server now submits news only on fetch or when a user joins.
There is no longer a way to coax the server for an update or to fetch.

Now I should be able to change the layout significantly!
Reorganize the page.

Oh yeah.
Server sends connection count to everyone as clients enter and leave.

No longer accepts 'connection_count' from the client. In fact, I believe
that the client no longer sends anything (apart from the socket.io
heartbeats, of course.)