If you're deploying this to an internal network, you might skip the step of creating an TLS certificate. This is problematic because getUserMedia won't work post-Chrome 47 for non-HTTPS connections.

Tuber should come with a set of helper utilities for creating a TLS certificate so this is less of a problem.

lol http://www.vidyo.com/

Rewrote the entire UI and underlying easyrtc implementation. It is working in my limited testing scenario but I would like another pair of eyes to take a look at it. At least, I hope it works as well as before and that the microphone/camera toggle buttons are more intuitive.

Currently, if a camera is not detected at the beginning of the chat, no audio will occur.

I must have forgotten to have set that as the default. It works after initial blur.

"Your browser has not been extensively tested. There maybe user interface artifacts or missing functionality."

Change this text.

js/vtc.js is modular enough to swap out with an alternate WebRTC library, like SimpleWebRTC, if it works more reliably than EasyRTC.

This might be nice for easier corporate deployments. Although tuber works fine on a flat corporate lan by itself, it would be better if this installation method included a stun/turn server too.

Create a framework for intercepting chat messages with the prefix '/' and allow for the implementation of custom chat commands.

First custom chat command should be one to "ping" either the room or a specific user in the channel. This "ping" should be done in the form of playing a sound and popping up a notification.

http://handlebarsjs.com/
It escapes the html by default

Currently, disabling the camera or microphone initially will disable the device for the entire duration of the video call. This is not ideal and probably confusing to the user. An ideal solution would be to only disable camera/microphone if the related device is not found. If the user voluntarily disables the camera/microphone, it should be toggle-able during the video call.

This should not be too difficult to implement. For initial camera/microphone disabling, we should have JavaScript that disables the camera/microphone immediately after getUserMedia.

• Add "slack-like" features (start with / commands)
• Change chat panel formatting

http://docs.travis-ci.com/user/languages/javascript-with-nodejs/

Implement a "dashboard" mode that shows all the callers (same sized video boxes) on one screen.

Hangouts generally starts with the video off, or asks before you want to join a chat. Maybe we can improve the call joining screen to let you configure video?

or some other kind of notification

key listener in JS

• Give peers the ability to mute other peers during a call (similar to Google Hangouts)

The current chat pane is 80/20 which might be a bit small, perhaps add a resizable pane (similar to IFRAME) or a button that changes the ratio to 60/40.

• Add functionality to look at remote DOM tree
• Maybe functionality to get remote events?

• If a user disables the camera feed, replace the "black screen" with a custom icon (similar to Hangouts)
• If a user disables the microphone, add some sort of visual on their viewport.

Should make a launch daemon plist that runs the server and logs output to a path.

A competitor has joined the game:

• Afternoon Citadel
• syscall

How can we detect instances where TURN/STUN all fails and no connection exists? I think vLine does something similar.

http://html5doctor.com/video-canvas-magic/
http://stackoverflow.com/questions/5059551/how-to-render-dynamic-bitmap-stream-to-canvas?rq=1
https://gist.github.com/yying/80c23fd0d62272e6c37b
http://html5demos.com/gum-canvas#view-source <-- might be more performant?

With vows or mocha or whatever people use these days. Travis-CI is already enabled for this repo, I just need to add in the button for it.

• If a stream is making noise, show a notification/indicator of some sort.

Should investigate?

https://github.com/trailofbits/tubertc/blob/master/server.js#L125-L146
See appIceServers: http://easyrtc.com/docs/guides/easyrtc_server_configuration.php

AFAIK the 3 most popular STUN/TURN servers are:

• https://github.com/otalk/restund (C)
• https://github.com/coturn/coturn (C)
• http://www.resiprocate.org/Main_Page (C++)

Guides

• http://www.html5rocks.com/en/tutorials/webrtc/infrastructure/#after-signaling-using-ice-to-cope-with-nats-and-firewalls
• https://www.webrtc-experiment.com/docs/TURN-server-installation-guide.html
• http://www.rtcquickstart.org/ICE-STUN-TURN-server-installation

There are a variety of ways to "bundle" a STUN/TURN server, but I think an Ansible script would work best.

Right now, if a user uses Chrome on Android and suspends the device (pressing the power button), the user is does not automatically hang up from the call. Is there a way to detect this scenario and force a hang up?

https://devcenter.heroku.com/articles/heroku-button

We need telemetry for determining which p2p connections are failing and why.

System setup:

• Ubuntu 14.04 desktop
• xubuntu-desktop
• CGC amd64 kernel (cgc kernel changes were not rebased onto ubuntu kernel sources, so this could just be a kernel issue).

How to duplicate:

1. Open up a tubertc video conference. Make sure sound is not muted.
2. Close tubertc.
3. Sound will now be muted.

The chat input field can scroll horizontally and refuses to return to the beginning cursor position after sending the message.