Add stun server fallback and I-told-you-so message if we get no TURN server and the connection fails.

Fixed SYWEB-36: use getUserDisplayName for disambiguating display name in member list and message sender name. This method is robust when disambiguation is no more required

Displayname are then disambiguate where it is necessary

match the normal response. Don't break if the turn_uris option isn't
present.

endpoint appropriately.

Hopefully implement turn in the web client (probably wrong for Firefox because Firefox is a special snowflake)

coturn.

SYWEB-27: Public rooms with 2 users must not considered as 1:1 chat room and so, they must no be renamed

Added hasOwnProperty tests when required to be robust to random properties added to he Object prototype

Continue to use presence data as fallback solution which is required when users do not join the room yet.
Created eventHandlerService.getUserDisplayName() as a single point to compute display name.

on safari at least keypress's event.which returns ASCII rather than keycodes, so 38 & 40 was swallowing ( and & rather than up-arrow and down-arrow(!)

use all new /rooms/<room id>/state to actually gather the state for rooms whenever join them. a bit ugly, as we don't currently have a nice place to gather housekeeping after joining a room, so horrible code duplication...

patch over another scenario whe we leak room IDs.  i have *zero* idea why or where the webclient is overriding message.membership to be "join" though, when it comes down the events pipe as "invite" (which was causing this failure mode)

Add support for TURN servers as per the TURN REST API (http://tools.ietf.org/html/draft-uberti-behave-turn-rest-00)

Swapped ng-keydown to a directive, which does the same thing (check if up/down
arrow then call history.goUp/goDown). This has *dramatically* improved
performance when typing in rooms which have lots (>100) of messages loaded.