131–140 of 161 posts
Who pays for the stun and turn servers?
A STUN server is used to get an external network address. TURN servers are used to relay traffic if direct (peer to peer) connection fails.
Could someone share practical usages of these commonly today to help me better grasp usage for these servers as a starting point?
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.
This is predominately USA mentality. In the rest of the world widespread use of carrier-grade NAT predates mobile networks by decades.
Many residential ISPs don't hand out public IPv4 addresses or require extra payment for them. Some of those ISPs got their first IP block (or even single address!) from someone and never bothered with whole "ask IANA for addresses" thing. It is multi-layer NAT all the way down.
Earlier quoted context omitted.
How exactly would they alter the desktop client I installed from a git clone?
If you wrote the client then they couldn't alter it, but then if you wrote the WWH site then they couldn't alter that either, so there's no difference. If you're running code from a clone of somebody's git repo you're vulnerable to anything they did to that code, just as if you're running code from a web site you're vulnerable to anything they did in that site. There are marginal differences, and I'm guessing the one…
I would not let employees at my company use an externally hosted site like this to share secrets. I would have no problem if it were hosted internally by the company.
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.
Earlier quoted context omitted.
I once tried sending a 3 GB file through it, then kept wondering why my entire system became so sluggish. Turns out it loads the entire thing into RAM... The file didn't go through either. I hope this one isn't like that.
Does HTML5 even let you read a file without loading it all into memory? Edit: Looks like this is it. https://developer.mozilla.org/en-US/docs/Web/API/ReadableStr... Edit 2: And yes, this is using it. https://github.com/saljam/webwormhole/blob/master/web/main.j...
There is still an open bug for large file transfers: https://github.com/saljam/webwormhole/issues/4
Earlier quoted context omitted.
This uses STUN servers to help it poke through NATs. (That's what I mean by "WebRTC's NAT traversal tricks") 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!
" but these seem to be relatively rare nowadays " AT&T 5G uses Symmetric NAT. It's not rare if you have an iPhone or iPad with cellular. No way to do P2P without relaying traffic unless you want to "guess" the randomized port number, and, on that front, there are NAT-device-aware algorithms that can make that process faster. We were promised IPv6 will make NAT's not necessary but I believe service providers use NATs…
They are zealously pushing the "ever increasing speeds" of questionable benefit for the user - what for? So that commuters could watch 8k 120fps video while on a bus? Or rather to gather all kind of sensor data in real-time, audio and video included, from their human oil wells? To strip off people's clothes with millimetre wave imaging?
But making it easy for people to run their own home/mobile servers, share and cooperate without govporate oversight is clearly not on their agenda.
Earlier quoted context omitted.
Things have changed (alot!) the last two years have seen a couple implementations come around. * https://github.com/pion/webrtc * https://github.com/aiortc/aiortc * https://gstreamer.freedesktop.org/documentation/webrtc/index... * https://github.com/rawrtc/rawrtc
Yo Where be at the Node.js verzhun?