We'd love to use it and appreciate your hard work though. Do you have any ideas on how that problem can be solved?
The more difficult part is probably detecting this lag. I'm not sure how this could be done. Maybe the node websocket server (ws) can detect congestion somehow.
MJPEG is supported in all browsers I know of, and would cut down on bandwidth by 33% over base64.
(If you really want to use WebSockets, a more dense encoding than base64 could also help - look into base85, for example.)
For this application you'd need it to be in an <img> tag anyway since there's the other stuff on the page too, so that's a moot point.
http://googleblog.blogspot.com/2012/05/next-step-in-chrome-o...
If you're having performance issues with it, you just have the video codec tuned wrong.
we'll check that out, thanks for the heads up.
The "video" quality is pretty bad though. From what I can see, the app streams base64 encoded JPEGs via WebSockets and draws them in a Canvas. The overhead of sending complete images costs a lot of bandwidth.
You may want to look into jsmpeg for live streaming: https://github.com/phoboslab/jsmpeg