Transfer.sh – Easy file sharing from the command line
1–10 of 88 posts
Re: Transfer.sh – Easy file sharing from the command line
#2Re: Transfer.sh – Easy file sharing from the command line
#3The service itself was broken for a very long time, did it become active again?
Re: Transfer.sh – Easy file sharing from the command line
#4This looks great, but does it survive solely on donations? For me that's the one important piece of info missing from the page.
Re: Transfer.sh – Easy file sharing from the command line
#5This stores files for two weeks on a third-party server.
What advantages for the intended use cases does transfer.sh have over netcat invented 26 years ago? I know some people who have used nc for those entire 26 years to xfer files point-to-point from the command line.
Re: Transfer.sh – Easy file sharing from the command line
#6This stores files for two weeks on a third-party server. What advantages for the intended use cases does transfer.sh have over netcat invented 26 years ago? I know some people who have used nc for those entire 26 years to xfer files point-to-point from the command line.
Not sure if your comment is just a re-hash of the now famous HN comment on the Dropbox Show HN ("Why can't you just use rsync/scp"), but netcat which is a unix utility shares basically nothing with transfer.sh which is a web based file sharing application. Comparing them is really apples-to-houses.
Netcat has it's uses, but one of them is not guiding your friends and/or family through a terminal in order for them to receive some photos you took last summer vacation.
Re: Transfer.sh – Easy file sharing from the command line
#7This stores files for two weeks on a third-party server. What advantages for the intended use cases does transfer.sh have over netcat invented 26 years ago? I know some people who have used nc for those entire 26 years to xfer files point-to-point from the command line.
Guess mostly nat penetration and storage for a few days
Re: Transfer.sh – Easy file sharing from the command line
#8This is exactly the use case for Magic Wormhole, which is what the cool kids use to transfer files:
https://github.com/magic-wormhole/magic-wormhole
Magic Wormhole uses an end-to-end PAKE to create an encrypted transport between two points in the Internet, using a rendezvous server.
It doesn't store files, which is almost never what you want; it's not a way to send a file and have 10 or 100 people download it. But it's probably the best way to get a file through a bunch of arbitrary network controls, NATs, &c to a desired destination. There's a Go implementation as well:
https://github.com/psanford/wormhole-william
... which is what I use most of the time. If you haven't played with it, I highly recommend it.
Re: Transfer.sh – Easy file sharing from the command line
#9I like transfer.sh and use it occasionally as an easy way to send things to friends that are on a remote server. However, I've realized that the upload speeds are pretty throttled to the point where it takes minutes for 100mb file. So I started using oshi.at which afaik is petty similar but faster uploads. Though, the one downside of oshi.at is that you can't watch mp4s in the browser it just starts download immediately.
I look forward to seeing a CLI for wormhole.app though
Re: Transfer.sh – Easy file sharing from the command line
#10This stores files for two weeks on a third-party server. What advantages for the intended use cases does transfer.sh have over netcat invented 26 years ago? I know some people who have used nc for those entire 26 years to xfer files point-to-point from the command line.
Netcat is seriously awesome, and still exists very much under the radar of a lot of people. I've used to to copy files around the planet, the datacenter, and the lab.
It excels at doing things "right now". If I have a terminal window open on a server in France and one in the US; then I can easily move that file. However, If I have to move my body to the target location before I can copy the file it doesn't work as well. (Need to jump through a few other hoops that make it more challenging.)
Protip: ALWAYS grab the hash of the file before you send it, and compare.
2nd Protip: Encrypt your file(s) before you send them.
Something like this is decent for moving a file at your leisure, or to give a copy to somebody else at their leisure.