So remove "port scanning" since the only difference between port scanning and "legitimate" connection attempts is rate. Should websockets be able to connect to

So remove "port scanning" since the only difference between port scanning and "legitimate" connection attempts is rate. Should websockets be able to connect to the local machine? In some cases that could be useful (even if something the kinds of people visiting this site might be uncomfortable with). E.g., a local daemon that listens for a websocket connection and a public web page that's used for managing it. I don't think it was implemented this way, but think something like Battlefield 3's matchmaking: the user visits the online service and finds a match to join, and when they want to join it passes the relevant information to the game via websocket. I imagine stuff like this has been implemented in at least a couple cases that you'd break just wholesale blocking connections to 127/8.