> You are known as Azure Bug Ok, that’s cute. I would perhaps delay showing the funny name until at least one other machine is detected, it makes it feel like

> You are known as Azure Bug Ok, that’s cute. I would perhaps delay showing the funny name until at least one other machine is detected, it makes it feel like my name is being broadcast over the public Internet for anyone to connect to, and not just a LAN connection, the way it is. But worked perfectly for me to send a few photos back and forth. LAN connections seem like the perfect application for WebRTC not having to deal with TURN or STUN. It is a bit unnerving that there’s no permission request before being able to do network discovery on the LAN however. How is one machine finding the other? Central server matching the public IP used to then share their private IP? Or does WebRTC provide a discovery service? Edit: Ok, Looking at the server code [1] there is indeed a “room” per public IP and the server passes messages between peers in the same room. [1] - https://github.com/RobinLinus/snapdrop/blob/master/server/index.js https://github.com/RobinLinus/snapdrop/blob/master/server/in...