gargron / baron Goto Github PK

The .wav ping file is too large and has audible static hiss above 11 kHz.

Currently the Contact object for the correspondent will stay in the "trying to connect" stay unless the user on the other end accept the offer in some way. Of course, if the other user declines the offer, or leaves the site, no feedback will be sent to the original caller.

For going offline, the solution is simple. Just reset the peer state as if on hangup. The offer to the other user will be lost anyway.

For declined offers, it's more complicated. If we implement a simple timeout on our end, after which we would reset the peer state, the other user might try to send us an answer to the offer at a later time, which would throw an invalid state exception and do nothing else.

Perhaps declines would need to be transferred through the signaling channel as well.

Add a UI action to block a contact, which would put the contact in a special state, removing it from the contacts list of the blocker and of the blocked person, and preventing any further contact requests to be shown to the blocker in the future.

The address to which the Socket.io client will try to connect is hardcoded, and cannot currently be set through environmental variables (ideal solution).

Through sounds and a blinking document title. Needs to go away when document is focused.

Instead of showing the offer/answer process to the user, try to automatically establish a data channel to user's contacts.

Store conversations in browser's memory, and allow synchronization on start-up.

Introduce abstractions that would choose available prefixes for WebRTC objects and handle browser-specific quirks.

Currently the last socket.io connection of a user to be established takes place in the user.sid property, and whenever a connection is closed, the sid will be set to null, even if the user is still online in a different tab.

This probably requires using an array for the sid property, and using socket.io rooms (user == room, all user's connections join a room, dispatch messages to user to that room).

Move data to a persistent database instead of storing them in memory. Currently a lot of pointers are being thrown around.

The fix at e36c842 didn't actually work because the accept callback passed to the event handler is inherently bound to the old peer connection.

It is basic functionality for a chat client to have a basic emote function.