Disable the ability to GET individualy messages. We need to think about the correct API to do this, as the current one doesn't make much sense.

Get presence for members when you enter a room (it was coming down but wasn't being stored in the right place)

Added infinite scrolling. It's sliiiightly buggy in that it jumps down the list a bit, but it is overall working pretty well. Added ng-infinite-scroll-matrix.js and jquery-1.8.3 as deps.

When new invites come down, update the My Rooms list. Added hacks to make the display name a bit nicer (/im/sync needs to return room aliases / membership events better)

Document that /rooms/:room_id/members/list yields profile and presence information about room members

Conflicts:
	synapse/storage/roommember.py

Fix imsync's SELECT query to only find the rooms I'm actually joined in, not every room I have ever joined

Remove old polling stuff from RoomController. Added service comments. Do not start the event stream on startup unless you have credentials.

Event streaming now happens on an app level, rather than a per-room level. Make eventStreamService manage it's own repolling provided no one calls stop() on it. Couple the stream with eventHandlerService so any controller can just blithely call eventStreamService.resume() and expect to 'get stuff' without having to handle promises (though resume() still returns a promise for that request and proxies it through $q). Kill and reset the stream if you logout.

Store messages in $rootScope so they can be accessed from multiple controllers without duplicated storage for each. This also gives updates.

Added event handler service which.. handles events. More specifically, it $broadcasts events depending on their type, and does processing on events (shuffling keys, adding events to $rootScope so displays will automatically update, sending delivery receipts, and so on). Some of this logic was previously contained in the RoomController, which fails the moment you add >1 room into the mix, hence requiring a Service to handle events, rather than having each individual controller maintain their part of the world.

Added event stream service which neatly blobs together requests / state for the event stream. This depends on matrix service to do the actual hit. Currently this has exactly the same behaviour as before.

Conflicts:
	synapse/storage/stream.py