21–30 of 161 posts
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?
Or has WebRTC made advances I'm unaware of?
We need a distributed db based on webrtc
Earlier quoted context omitted.
I blame NAT. Treating end-users like second-class netizen consumers trained people to "need" the cloud to do perfectly normal peer-to-peer things.
I'm not sure I would blame NAT. You can easily disable that. What you can't disable is the asymmetry of consumer internet connections (upload << download) and the fact that most consumer devices are not running (or connected to the internet) 24/7.
file.pizza is another similar project
Nice, I made one of these a few years ago http://passfiles.com Yours is a bit more polished than mine though. I didn't use QR codes either just good old fashioned urls.
> ...it uses WebRTC to make the direct peer connections. This allows us to make use of WebRTC's NAT traversal tricks, as well as the fact that it can be used in browsers. 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? Or has WebRTC made advances I'm unaware of?
I would love to see TCP hole punching in ICE, but it sounds like it is super hard to get right.
Consumer internet does a lot better, lots of those failures come from Government/Military/Medical I bet.
This is fantastic! Really nice work :) The nice thing about WebRTC is this works (pretty much) everywhere! Someone could throw up Python/Android/iOS/Go/Web/C++ Clients really easily. That is really exciting. Also just a HUGE fan of NAT Traversal/P2P in general. The less dependence we can have on others for sharing our data the better.
Huh, what did I miss?! How do you make a WebRTC-client in language-of-your-choice? The last time I checked for C++ I only found answers like "look at the chrome source". lol.
file.pizza is another similar project
> ...it uses WebRTC to make the direct peer connections. This allows us to make use of WebRTC's NAT traversal tricks, as well as the fact that it can be used in browsers. 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? Or has WebRTC made advances I'm unaware of?
There's no TURN server set for this, but it shouldn't be hard to add one. There are NATs where you'd need one to relay all the traffic, but these seem to be relatively rare nowadays. If anyone has any actual statistics on these I'd appreciate it!