Live data from Hacker News

I built a browser-based P2P file transfer tool using WebRTC

airdows.com

11–20 of 25 posts

Re: I built a browser-based P2P file transfer tool using WebRTC

#11

You have some web page material in English, and some material in either Spanish or Portuguese. You might want to check everything twice before posting on HN.

you're right, AirDows started as a Spanish first beta, and some pages are not fully localized yet, i'm fixing the language consistency before the next round of promotion thanks for pointing it out

Re: I built a browser-based P2P file transfer tool using WebRTC

#12

You have some web page material in English, and some material in either Spanish or Portuguese. You might want to check everything twice before posting on HN.

Not the poster but I had to go check the website to see this. I believe it is in Spanish. It makes me pretty happy to realize that even though I have had little or no conversations with Spanish speakers for about 30 years I was able to understand the untranslated text. There is so much that clicked once I had the context through the words that I recognized. The rest of it began to make sense. Thanks for that mental e…

that's genuinely nice to hear. Thanks for taking the time to explore it despite the language mismatch, a consistent English version is coming

Re: I built a browser-based P2P file transfer tool using WebRTC

#13

What happens when TURN is inevitably needed? Many people are behind something like CG or symmetrical NAT with no direct way to talk to each other. There are no reliable, fast AND free TURN servers (IMO), and even semi-private relays can quickly become overwhelmed or too costly to operate.

thats one of the main operational challenges. AirDows attempts a direct connection first and only uses TURN when NAT conditions require it. I'm already measuring relay usage and evaluating sustainable TURN providers and limits while keeping the beta free...

Re: I built a browser-based P2P file transfer tool using WebRTC

#14
Does anyone know what the actual success rates for webRTC are for like different NAT combinations / nodes in the wild? I'd be curious, I have read a little into it myself but didn't get the feeling it was very flexible compared to something like Tailscale.

Re: I built a browser-based P2P file transfer tool using WebRTC

#15
https://gist.github.com/SMUsamaShah/fd6e275e44009b72f64d0570... I keep a handy list. Does this stream file directly to disc or keep it in browser cache or memory? In this list I think only web wormhole does that which means it should be able to transfer huge files without any problem. Most tools crash if files are in GBs.

Re: I built a browser-based P2P file transfer tool using WebRTC

#19

https://gist.github.com/SMUsamaShah/fd6e275e44009b72f64d0570... I keep a handy list. Does this stream file directly to disc or keep it in browser cache or memory? In this list I think only web wormhole does that which means it should be able to transfer huge files without any problem. Most tools crash if files are in GBs.

I went down the list a couple weeks to go trying to move files from my windows desktop to my Chromebook and the only thing that worked in the top 5 or 10 was localsend.

So many of these tools just silently fail. And there's so many of them!

Re: I built a browser-based P2P file transfer tool using WebRTC

#20

https://gist.github.com/SMUsamaShah/fd6e275e44009b72f64d0570... I keep a handy list. Does this stream file directly to disc or keep it in browser cache or memory? In this list I think only web wormhole does that which means it should be able to transfer huge files without any problem. Most tools crash if files are in GBs.

Thanks for keeping the list going. I link to it on here now and again.
Post reply on HN