The various browsers decided that webrtc (websockets as well) didn't need to follow the "same origin" rules that they set up for XmlHttpRequest.
It almost feels like browsers should have some way to delineate "web pages" from "web applications" and provide different ways to present them to end users, different rules, etc.
For now, I have disabled WebRTC in FireFox by setting media.peerconnection.enabled to false in about:config.
At some point, it's much closer to an "App Store", which arguably has finer grained (and more usable) control presented to the user to manage what applications can (and cannot) do.
I also doubt it would hold in court. TOS have a very restricted applicability. You can not use them to restrict people's rights in unexpected ways.
Given that they are selling a CDN, and thus likely want to sell to globally operating customers, that might become relevant relatively quickly.
Since among the HN users there are probably a lot of developers, I tried to put some of the IPs into my browser. And indeed, already the second IP I tried sent back a reply from a (misconfigured) server.
I have to say it feels frightening, that the other users can see my IP. And probably other data about me.
Also I would expect it's not legal in most places around the world to give away the IP of a visitor to other visitors. Can't imagine it is legal in Europe.