While we're speculating about trust and such, the video mentions that it's a browser extension which connects to a trusted peer and uses the peer as a proxy. This leads me to believe that,
1. Since it's a normal browser extension, the source will be readable and verifiable.
2. It probably uses WebRTC.
It seems Google merely plays an incubator role here for the authors. Either way, I don't see much trust issues that other comments are complaining about.
Looking forward to trying this out when it's released.
that's all well and good, but if it's executed by an unverifiable binary build of Chrome (i.e. the one distributed by Google), it's not worth much. For what you know, Chrome might just detect the extension is installed and silently eavesdrop on all its calls.
If this extension will work as-is on third-party Chromium builds compiled from public sources, then yeah, it can be trusted on those builds.
You say that like it probably won't. They state in the FAQ that it will work on FF and Chrome; there's no reason to think it won't work on Chromium as well.
The source code will be released by the University of Washington under the Apache 2 license after the trusted tester phase is completed. If you would like to get involved sooner go to http://uproxy.org/#join
1. Since it's a normal browser extension, the source will be readable and verifiable.
2. It probably uses WebRTC.
It seems Google merely plays an incubator role here for the authors. Either way, I don't see much trust issues that other comments are complaining about.
Looking forward to trying this out when it's released.