rdv VS croc

Haha that’s currently a way to explain to people who are used to hosting/sync based cloud solutions that anything that is (a) local p2p and (b) doesn’t need to upload-before-download is much faster. It’s also faster than WebRTC based solutions which there are dozens, WebRTC kind of sucks for large stuff.

That said, the next version will have multi connection tcp striping, which is a lot faster than any single tcp solution in many cases, especially over long distances, similar to some ftp/usenet clients. (Spoiler there will be online p2p transfers. See https://github.com/betamos/rdv if curious)

This is an incredible resource on NAT traversal in practice. I used it as a reference while building a server-assisted p2p-over-TCP[1] system. The post covers UDP but all of the theory applies to TCP as well – you just need some SO_REUSEPORT dual dial/listen magic so the code will look a bit different.

The post alludes to this, but I think NAT traversal is an inaccurate and confusing term. I like “hole punching” a lot more as a general term. It gets the message across without the myopic connotation that it’s all about NATs – it isn’t.

[1]: https://github.com/betamos/rdv

> In trying to come up with a WebRTC solution, I think I've settled on defeat. The local network syncing works like a charm, but I haven't had any luck in trying to get around a TURN server by using an API endpoint to provide routing data. It would be nice if there were other prebuilts than COTURN (something deployable to a deno/node server would be ideal),

The bad news is that if you want something that works in all instances, you need a relay of _some_ sort, because p2p isn't possible/feasible in all cases. Bittorrent (for instance) works around that limitation by simply having many-to-many peering and relying on large numbers, to be reliable. But that doesn't work for 1:1.

The good news is that maintaining a relay (or TURN, with WebRTC), need not be expensive. Yes, you need a server, and perhaps some IP-based rate limiting, but that can handle a LOT of connections and small data.

I created https://github.com/betamos/rdv for this purpose, an extremely light-weight alternative to WebRTC, but for TCP only (BYO identity, auth and encryption). The p2p success rate is, anecdotally, very high. However, you cannot use it from a web browser.

Feel free to reach out (see profile), happy to chat about p2p whether or not you use this project.

This very hn entries is bust contradicting your statement.

Also what about syncthing[1] (for recurrent/permanent sync) and croc[2] (for one time copies) ?

I have used both for a number of years already.

[1] https://syncthing.net/

[2] https://github.com/schollz/croc

Check out croc, I've been using it for years, and it works pretty great too!

https://github.com/schollz/croc

I'm trying to find very specific software.I need CLI(!!!) tool like Croc to share files using P2P, but it's very inconvenient to ask people to install same software as me(Croc in this case). Instead i want to get direct download URL, so anyone can download it just by using browser.

Related projects:

- FlyingCarpet: direct transfer over local adhoc WIFI: https://github.com/spieglt/FlyingCarpet

- LANDrop: Drop any files to any devices on your LAN: https://github.com/LANDrop/LANDrop

- In-browser file transfer similar to Airdrop: https://snapdrop.net/

- Magic Wormhole: simple file transfer from computer-to-computer over the net: https://github.com/magic-wormhole/magic-wormhole

- Croc: similar to magic wormhole: https://github.com/schollz/croc

- Wormhole: user-friendly in-browser based e2e encrypted file transfer: https://wormhole.app/

There’s already the excellent [croc](https://github.com/schollz/croc) which I’ve gotten all my friends to install and use.