Peer-to-peer file transfers in the browser

Post by tripflag » Mon, Mar 17, 2025, 12:16 PM UTC

apitman wrote: post #253

tripflag wrote: post #186

Earlier quoted context omitted.

> There are services which allow you to upload via CLI and download via web browser, but they host your file so you have to wait for the full upload to finish before sharing the link. There are exceptions to this; I've been making copyparty[1], an httpd which lets you start downloading a file that is still being uploaded[2]. If you catch up with the uploader, it'll throttle the speed so the browser doesn't drop the c…

Why throttle the browser rather than just having it block until more data arrives?

if you stop sending data entirely, browsers tend to drop and reopen the connection after a few minutes, assuming something got stuck along the way. Throttling seems to prevent that nicely.

Post by nikisweeting » Thu, Mar 20, 2025, 6:28 AM UTC

saurik wrote: post #266

nikisweeting wrote: post #219

Earlier quoted context omitted.

> A symmetric NAT is one where all requests from the same internal IP address and port, to a specific destination IP address and port, are mapped to the same external IP address and port. My understanding is that it's not "required", but most of the CGNAT routers I've encountered do symmetric NAT, and they force-randomize the source port for each new connection, then keep it fixed for one external ip:port for some "s…

Such CGNAT should also be more likely to support PCP than a normal NAT. It does suck that, AFAIK, no browser has integrated support for this into their WebRTC stacks :/.

TIL about PCP, didn't realize anything came after NAT-PMP!

and also wow I'm honored to get a reply from a childhood hero of mine. I've been a diehard Cydia fan since 2010!

Re: Peer-to-peer file transfers in the browser

Re: Peer-to-peer file transfers in the browser