Update in follow-up post.It loads now - guess it was just down temporarily and I got unlucky.
Great!
I think this is a really interesting approach and your UI is great, so congratulations there. You might want to avoid using the custom E symbol outside of the logo though. Seeing it show up in the currency list is a bit jarring.
Makes sense, we'll work to clean things up re: typography. Thanks for the feedback!
Using WebRTC as a way to do P2P traffic in a browser is a really neat hack, even if it's basically using Chrome as an app platform for now. How does it work with NAT? Do we end up bouncing connections off reflector servers, or does it use UPnP?
NAT traversal shouldn't be a problem, barring a blocked port. Basically what happens is there is what's called a STUN server that helps each individual peer know their public IP and port. The ID that the user assigns itself (done automatically), becomes the route to communicate with that user. All communication is done directly peer-to-peer via JSON calls. We have our own schema for how those JSON calls are structured.
That said, whilst I think there's great potential for WebRTC for p2p bitcoin browser apps, I'm not sure a localbitcoins competitor is the right place to start. The fact that my ad disappears if I close my browser window is rather questionable. Also, presumably if I leave it open all the time (e.g. at work) then at weekends I have no way to see messages that get sent to me, etc. This sort of thing really needs persistent storage and asynchronous messaging, like email.
Many other apps that are more real time in nature could benefit from your approach though.
We're working on a method to handle persistence, but haven't yet implemented this. We already have the functionality basically spec'd, but aren't yet sure with what release it makes the most sense for.
