> But I'm assuming it can't break through all NAT routers, right? A good portion of people still won't be able to use this?
> A service usable by everyone would require STUN and TURN servers to be set up, no?
Anecdata, of course, but I haven't been able to reliably use any of these WebRTC based file transfer services (file.pizza, instant.io, etc etc). Testing mostly between two computers on the same subnet. Sometimes they work for a little while, at surprisingly low speeds (for two computers connected to the same wireless access point), sometimes I can let them sit for an hour and never get a connection. I've learned to not even bother trying them, it just wastes time.
That said, magic-wormhole (the original) works fine between the same devices, so maybe I'll see if something is somehow different about this implementation.
Edit: ah yes, this service hangs indefinitely on "connecting". You love to see it. (Firefox on Linux - firewall disabled specifically for this test - and Safari on macOS)
Edit: seems to be working in Chrome (Linux) to Firefox (Android). Not sure what the difference is.
I developed it mainly on Firefox on macOS. I'd love to figure out why it didn't work for you. Do you get anything on about:webrtc while trying to connect?
Thanks for the reply. I did the following for you:
1. Opened about:webrtc, clicked "start debugging".
2. Opened a WebWormhole on one tab.
3. Copy / pasted the code into WebWormhole on another tab. Got something like "invalid key".
4. Try again steps two and three. Got endless "connecting" message this time.
5. Stop debugging. No log file /tmp/WebRTC.log was created, so I clicked "save page". Used sed to replace my public IP address with x.x.x.x and uploaded here for you:
I hope this gives you enough information to fix the problem. I'd like to be able to use these tools too. I suppose it could be addon related, but another user confirmed the problem for Firefox / Linux. It would be useful to be able to detect various problems and report them to the user instead of hanging on "connecting".
> A service usable by everyone would require STUN and TURN servers to be set up, no?
Anecdata, of course, but I haven't been able to reliably use any of these WebRTC based file transfer services (file.pizza, instant.io, etc etc). Testing mostly between two computers on the same subnet. Sometimes they work for a little while, at surprisingly low speeds (for two computers connected to the same wireless access point), sometimes I can let them sit for an hour and never get a connection. I've learned to not even bother trying them, it just wastes time.
That said, magic-wormhole (the original) works fine between the same devices, so maybe I'll see if something is somehow different about this implementation.
Edit: ah yes, this service hangs indefinitely on "connecting". You love to see it. (Firefox on Linux - firewall disabled specifically for this test - and Safari on macOS)
Edit: seems to be working in Chrome (Linux) to Firefox (Android). Not sure what the difference is.