> Those are present here but not the largest threat. This service apparently makes you download ~300MB you have no idea what is and SHARES it in the background. What if it is child abuse content? This isn't even a "think of the children" argument, it can have very real consequences to anyone cluelessly browsing the web unlike your usual p2p network.
HN can upload 300 MB of child abuse content to your computer. WebRTC is not required for that. Even JavaScript is not required for that, create tiny 1px images and link those to (un)desired content, they'll be cached in your browser according to cache headers, possibly infinitely. That's the nature of the web: you have very little control over your browser, unless you'll scrutinize every HTTP response which nobody does.
> WebRTC has additional insecurities and deanonymization potential like VPN leaks.
Legitimate issues should be fixed or put behind prompts, I agree with that. But issues inherent for Web should not be blamed for WebRTC IMO.
HN can upload 300 MB of child abuse content to your computer. WebRTC is not required for that. Even JavaScript is not required for that, create tiny 1px images and link those to (un)desired content, they'll be cached in your browser according to cache headers, possibly infinitely. That's the nature of the web: you have very little control over your browser, unless you'll scrutinize every HTTP response which nobody does.
> WebRTC has additional insecurities and deanonymization potential like VPN leaks.
Legitimate issues should be fixed or put behind prompts, I agree with that. But issues inherent for Web should not be blamed for WebRTC IMO.