Ask HN: What is your favorite method of sending large files?

Post by myself248 » Wed, Sep 02, 2020, 9:48 PM UTC

livueta wrote: post #86

Bittorrent. No, really. Lots of nice behaviors when transferring large amounts of data between arbitrary endpoints. Transferring the torrent metadata is pretty trivial and can be done via a wide range of methods, and having that flexibility can be nice. Unlike HTTP, you get reasonable retry behavior on network hiccups. Also, more robust data integrity guarantees, though a manual hash test is probably a good idea eith…

Post by ahsima1 » Wed, Sep 02, 2020, 9:51 PM UTC

parliament32 wrote: post #117

enriquto wrote: post #108

Earlier quoted context omitted.

piping through tar is my "power move" when I want to steer a new recruit. I just do it casually in front of them... depending on whether they are awed or horrified by that, they'll get more hacky or more formal work.

You can also pipe through gpg if you want encryption along the way!

Post by myself248 » Wed, Sep 02, 2020, 9:52 PM UTC

Matthias247 wrote: post #75

ashton314 wrote: post #55

Netcat: $ nc -l 4242 > dest And then on the sending end: $ nc hostname 4242 This works great when you just need to get a file of any size from one machine to another and you’re both on the same network. Are used this a lot at one of my offices to schlep the files around between a few of the machines we had.

and if you are not worried about corruption. You might at least want to run a checksum on both ends and compare them.

Post by aargh_aargh » Wed, Sep 02, 2020, 9:54 PM UTC

libertine wrote: post #96

livueta wrote: post #86

Bittorrent. No, really. Lots of nice behaviors when transferring large amounts of data between arbitrary endpoints. Transferring the torrent metadata is pretty trivial and can be done via a wide range of methods, and having that flexibility can be nice. Unlike HTTP, you get reasonable retry behavior on network hiccups. Also, more robust data integrity guarantees, though a manual hash test is probably a good idea eith…

Sometimes I wonder if the bad connotation due to piracy made this protocol not standard (in a sense, that's not widely adopted, and people need dedicated clients, instead of it working for example in browsers). I don't know enough, maybe it has security issues, or some limits... but the fact is that it's still widely used, by tech literate people, so it still stands the test of time and it must be doing something rig…

Post by rootsudo » Wed, Sep 02, 2020, 9:57 PM UTC