Live data from Hacker News

Transfer.sh – File sharing from the command line

transfer.sh

71–80 of 117 posts

Re: Transfer.sh – File sharing from the command line

#71
post #59

Earlier quoted context omitted.

Could you please go into details like what's basic difference b/w static binaries and apps which use dynamic linking. What are the benefits of one over another? Something like grokking this concept for once and all :D

Pros: * single binary that you can scp (or use transfer.sh haha) into the production machine and run; no runtime environments, package installation etc. * two different applications can depend on different versions of a library without any intermediate package manager or virtual environment * guaranteed execution: related to the first point, but I see enough merit in this to make it a separate point Cons: * If there'…

One more con: shared libraries can be shared in memory; static binaries cannot.

Re: Transfer.sh – File sharing from the command line

#72
post #2

They really should’ve used some end to end encryption to protect themselves against DMCA bullshit. As it stands they will be abused for copyright infringement and the rights holders will not only ask for the files to be taken down, but for them to preemptively prevent those same files from being uploaded again. A huge rabbit hole full of bullshit.

This is the first thing I was wondering about as far as what the intended/eventual use-case of this tool is. The website and GitHub page doesn't go into a lot of detail for what it's intended to replace.

If I'm not confusing matters, in the past people might have sent files to each other by dropping stuff off in an ftp directory, or they might have used DirectConnect to host files up, or even Windows file sharing / samba.

If it were designed to be used within a local network on the other hand between untrusted users, it might make more sense but I think there would then also be simpler ways to go about that?

Re: Transfer.sh – File sharing from the command line

#74
post #66
post #40

I like it! But for me ssh already provides a simple and secure way to move files from one place or another.. tar -cf - ./files.txt ./orDir/ | ssh host "(cd /dest/dir; tar -xf -)" Given that ssh it so ubiquitous I think this will always be my go to.

> ssh already provides a simple way :-D > tar -cf - ./files.txt ./orDir/ | ssh host "(cd /dest/dir; tar -xf -)" :-O

reminds me of this gem https://news.ycombinator.com/item?id=9224

Re: Transfer.sh – File sharing from the command line

#75
post #40

I like it! But for me ssh already provides a simple and secure way to move files from one place or another.. tar -cf - ./files.txt ./orDir/ | ssh host "(cd /dest/dir; tar -xf -)" Given that ssh it so ubiquitous I think this will always be my go to.

What about good old scp? scp file.txt user@host:/dest/dir/

I usually go straight to tar & ssh over scp since you can do directories where you can't with scp. But yeah, if you just have some files scp works.

Re: Transfer.sh – File sharing from the command line

#76
post #61
post #40

I like it! But for me ssh already provides a simple and secure way to move files from one place or another.. tar -cf - ./files.txt ./orDir/ | ssh host "(cd /dest/dir; tar -xf -)" Given that ssh it so ubiquitous I think this will always be my go to.

This particular tool seems useful for sharing files with people who might not be comfortable with the command-line, or where you don't have an account on the receiver's computer, since it produces a regular http link to download the data.

That makes sense, I hadn't thought about that.

Re: Transfer.sh – File sharing from the command line

#77

Earlier quoted context omitted.

> tar -cf - ./files.txt ./orDir/ | ssh host "(cd /dest/dir; tar -xf -)" You should use '&&' instead of ';' on the host side. That way you don't accidentally dump your transfer contents into a wrong directory if the existing host dir doesn't exist. e.g.: tar cf - stuff | ssh host "(cd /dest/dir && tar xf -)"

Or just skip the shell entirely: tar -C /dest/dir -xf -

Yeah that's the right way to do it, but I always forget which flag it is for tar and this is faster than pulling up the manpages ;)

Re: Transfer.sh – File sharing from the command line

#78
post #40

I like it! But for me ssh already provides a simple and secure way to move files from one place or another.. tar -cf - ./files.txt ./orDir/ | ssh host "(cd /dest/dir; tar -xf -)" Given that ssh it so ubiquitous I think this will always be my go to.

> tar -cf - ./files.txt ./orDir/ | ssh host "(cd /dest/dir; tar -xf -)" You should use '&&' instead of ';' on the host side. That way you don't accidentally dump your transfer contents into a wrong directory if the existing host dir doesn't exist. e.g.: tar cf - stuff | ssh host "(cd /dest/dir && tar xf -)"

Good point!

Re: Transfer.sh – File sharing from the command line

#79
post #75

Earlier quoted context omitted.

What about good old scp? scp file.txt user@host:/dest/dir/

I usually go straight to tar & ssh over scp since you can do directories where you can't with scp. But yeah, if you just have some files scp works.

You can obviously send directories with scp, just use -r. Or am I missing something?
Post reply on HN