Excuse Me Sir, Your WebRTC Is Leaking

Re:Excuse Me Sir, Your WebRTC Is Leaking by softdev12 on Thursday February 26, 2015 @11:15AM (#9113263)

This is interesting and seems to indicate that there is a small edge case for people who want as much privacy as possible.

The larger topic for me is that webRTC has to make tradeoff for developers. And, I for one, love what it does. If you look at legacy comms development in the peer to peer space (e.g. Skype) the process was orders of magnitude more difficult than using a webRTC implementation. So, as a developer, sacrificing a prompt that grants an IP detection notice seems like a worthwhile tradeoff.

Also, I think webRTC is still in draft form and is still being modified in working sessions (although I'm not 100% sure of this). It would be great if Apple would get on board with webRTC for ios.

[ Parent | on HN ]

Re:Excuse Me Sir, Your WebRTC Is Leaking by Golgi_SDK on Thursday February 26, 2015 @11:41AM (#9113421)

I agree that WebRTC is very powerful and makes peer-to-peer communication from browsers easily accessible for developers. And I also love what it does. However, the issue raised in the post is seen from the point of view of the user. Convenience for the developer probably won't be a concern to a user who is concerned about IP leakage. Yes, the WebRTC API is still being standardised so perhaps this issue will be addressed in future

[ Parent | on HN ]