WebRTC Copy – OTR and fast file transfers over WebRTC

The problem with sites like these are that you have to trust the site owner to not just add some javascript to the page which breaks the security of your conversation.<p>Except this site is worse, because they also let their third party user tracking provider run arbitrary script on every page too.<p>Nice as a demo of technology though.

Can anyone explain please, whether WebRTC is a protocol or not? After reading this: <a href="http://www.webrtc.org/faq#TOC-Why-should-I-use-WebRTC-" rel="nofollow">http:&#x2F;&#x2F;www.webrtc.org&#x2F;faq#TOC-Why-should-I-use-WebRTC-</a> I thought it&#x27;s just an API to enable other protocols (XMPP&#x2F;Jingle, SIP etc.) to be built through JavaScript. Or is it a protocol after all?

Security issues are one thing, but I&#x27;ve been using this site as a simple way to transfer (nonsensitive) large files without having to wait for the file to go through a third party server, sit through the ads required to pay for the bandwidth for such a server, or require the recipient to download specialized software for a P2P transfer. For this purpose it&#x27;s very convenient.

You know what they say about javascript browser crypto, but for what it&#x27;s worth, it worked fine for transferring a file from my desktop to my phone (Firefox on both ends).<p>I wonder: when using WebRTC between two devices on a single LAN, is my ISP involved (possibly: beyond bootstrapping the process)?

It would be lovely if it would explain what features it needs out of Chrome Canary.