webrtc

So does that mean the WebRTC issues will be made visible to the average user?

See the difference is that you explicitly use WebRTC.

Although perhaps more constraining, why not use a website that uses WebRTC data channels to transfer the files?

Same with WebRTC - your internal network's IP is not the kind of privacy most people care about, nor should they.

That said, WebRTC from behind a VPN exposing your personal IP is a bit different.

Ofc WebRTC is based on SIP, but with who knows how many additional layers.

Maybe WebRTC, but no one is making a commercial service out of that yet.

For me the greatest limitation of mobile safari is the lack of WebRTC.

If you attack scenario is trying to circumvent authoritative governments, don't use a web browser with extra features or plugins like WebRTC turned on.

Your next post should be about how WebRTC steals your bandwidth.

The author of the website explicitly uses WebRTC, not you.

Most of the webRTC-based videochat services (Firefox Hello, talky.io, etc) use a server to deliver the client page and also relay these offer messages to the right party.

Again, WebRTC does not "barf" out your real IP in a VPN situation -- it barfs out the VPN's internal IP, which is meaningless to anyone except for the VPN's operator (and they have that data anyway).