Why Chrome only?
Which block do you rely on that isn't supported by Firefox?
<a href="http://iswebrtcreadyyet.com/" rel="nofollow">http://iswebrtcreadyyet.com/</a>
Cool; support is limited. I like to think we did better at Sococo.com - we support dozens of simultaneous participants, a dedicated client and web clients too.<p>Here's a picture of Teamspace at work: <a href="https://www.dropbox.com/s/nb5tqqeux0n1xep/SococoMtg.png" rel="nofollow">https://www.dropbox.com/s/nb5tqqeux0n1xep/SococoMtg.png</a>
We meet like this all the time; there were 23 people in that virtual room, 7 sharing webcams and one webcam in our central office. 2 documents were being shared, a common chat thread was going on. Probably many p2p chats going on; I couldn't see that as they're private.
<i>Hutt works exclusively (for now) with Chrome.</i><p>Useless crap. There's dozens of other WebRTC apps out now that support all WebRTC browsers and interop. Why should I use a clearly inferior one?
It just hangs on the "building your Hutt" page for me. Either it's swamped, or my company is blocking WebRTC somehow. Is there any way to verify WebRTC availability?
well my roommate has made this also video chat over webRTC<p>check <a href="http://easymeeting.us/hello" rel="nofollow">http://easymeeting.us/hello</a><p>hello is the room name which you could setup by accessing it