pthatcherg

14 ms·

121.
by pthatcherg 13y ago
FYI, Years ago I worked at a startup which made a distributed, p2p automatic file synchronization system. The startup didn't work out, but the system (mostly) worked. We spent a lot of time trying to solve things that are not largely
122.
by pthatcherg 13y ago
Why do you think WebRTC puts too much power in the hands of a few companies? It's completely open source and can do everything you want. You can take all the source code from either webrtc.org or chromium.org and use it to build your
123.
by pthatcherg 14y ago
Actually, the respective Mozilla and Google WebRTC teams get along quite well. I work at Google on WebRTC, and from what I've observed the joint work as been close, and always positive.
124.
by pthatcherg 14y ago
I think Google+ Hangouts are pretty good :).
125.
by pthatcherg 14y ago
It's true that the audio, video, and data are all encrypted. But it's not the case that you can send audio and video over the data channel. Well, you could send audio and video data, but there's no way to pipe audio and video data into th
126.
by pthatcherg 14y ago
It's not quite that simple. We (I work with the Chrome team) have an RTP-based data channel (sort of what you call "tunnel through the video" already in Chrome), but it provides no congestion control or reliability. To provide those, the
127.
by pthatcherg 14y ago
Firefox has as full DataChannel implementation (SCTP-based), while Chrome has a partial one (RTP-based). They don't interoperate yet. I implemented most of the partial implementation and am working on the full implementation now. I'm glad
128.
by pthatcherg 15y ago
Google+ Hangouts have screensharing as well.
129.
by pthatcherg 15y ago
That's funny. I implemented almost the exact same thing a few years ago, although mine is arguably more complete :) https://github.com/pthatcher/pyrec Here's my original post about it: http://www.valuedlessons.com/2009/10/introducing-py
130.
by pthatcherg 15y ago
Article didn't mention it, but Justin's blog post did: "Standards-based: XMPP, Jingle, RTP"... We're working on publishing the spec, which should be available soon. In fact, it's already implemented in libjingle: http://code.google.com/p/
131.
by pthatcherg 15y ago
Don't Yahoo and DDG use Bing for their search results? If so, Bing is the only alternative on your list.
132.
by pthatcherg 15y ago
Yes, complimentary. You could use WebRTC to implement a Jingle client.
133.
by pthatcherg 15y ago
We care about gmail on all browsers :).
134.
by pthatcherg 15y ago
I don't know how Obihai works, but if it uses SIP to talk to Google Voice, this will not effect them.
135.
by pthatcherg 15y ago
My original email had more details: We are pleased to announce that we have launched support for Jingle XEP-166 and XEP-167 for Google Talk calls to and from Gmail, iGoogle, and Orkut. We have also added the same level of support to libjin
136.
by pthatcherg 15y ago
In relation to #2 and #3, I think you underestimate how hard it is to get a p2p connection. It's very hard, and sometimes impossible, which is why a TURN server will often fallback to simply relaying data, in which case someone running the
137.
by pthatcherg 15y ago
The jingle portion of WebRTC comes form libjingle, and is usable right now with Google Talk. There is also a second open source implementation that works with Google Talk called "telepathy". http://code.google.com/p/libjingle http://tel
138.
by pthatcherg 15y ago
Gmail's voice and video chat now supports the main Jingle standards, XEP-166 and XEP-167. And there are two open source implementations that it works with: http://code.google.com/p/libjingle http://telepathy.freedesktop.org/wiki/
139.
by pthatcherg 15y ago
Actually, the standard deviated from the original implementation, as Google Talk pre-dated the standard. Either way, we're working on it. Also, the mobile version uses the same protocol as all of the other products (such as gmail). You ca
140.
by pthatcherg 15y ago
That is correct. We are working hard on it. By the way, libjingle, the Open Source library for writing jingle applications, already mostly speaks XEP-166 and XEP-167. We're still working on XEP-176, though. http://code.google.com/p/libj
141.
by pthatcherg 15y ago
Google Talk on Android uses the same XMPP-based signaling as all the other Google Talk products (gmail, the win32 app, etc).
142.
by pthatcherg 15y ago
Google also uses ICE-UDP and STUN, although the implementation was done before ICE-UDP was standardized, so it doesn't quite follow the standard yet. Also, Google speaks many audio codecs, including speex. ISAC (the codec from GIPS) is jus