5 ms·
But inside the browser, how do you actually verify the media path is secured properly? You end up trusting the server of the webpage you're on, since that's wha
by MichaelGG 11y ago
But inside the browser, how do you actually verify the media path is secured properly? You end up trusting the server of the webpage you're on, since that's what negotiates everything. And if you trust the server, then you can just offload things to the server in the first place, and going P2P doesn't really matter.
Outside of the browser, sure you can negotiate your own way and tie the media to an established key.
- fulafel 11y agoIs that different from trusting whatever system delivers your desktop/mobile apps? Download over HTTPS from an reputable app store or web site. Or embark upon building and verifying it from source, which you can also do in the web app case. The only thing that is missing is the ability to verify the download out of band on desktop. This might be addressed with a link/bookmarklet w subresource integrity? With the client side web app there is still more transparency than a server side app, because in event of compromise the backdoored code must be served to your browser instead of staying invisible in the backend servers. The other big advantage from P2P is operational independence, you no longer need anybody to bankroll the servers and bandwidth.
- tracker1 11y agoI did mention that something (such as electron, nwjs, or xulrunner) could be used as a distribution mechanism for desktop... likewise there are options (cordova etc) for mobile. No, it wouldn't/shouldn't be a dedicated app, as a proof of concept, but could be very usable in that form.