Live data from Hacker News

Transfer.sh – File sharing from the command line

transfer.sh

31–40 of 117 posts

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

#31
post #20
post #13

Can it have a little more security please? E.g. longer filename, more difficult to guess. And an encryption option would be nice.

Stop complaining and encrypt your stuff. You're the one making absurd requests to a fine small nice service here.

Not every feature request or suggestion is "complaining" or "absurd", even if it isn't worded perfectly.

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

#33
post #9

On a related note, I recently learnt that if you're on the same local network, there's a much faster way to transfer than the old tar|nc trick[0]: udpcast. You do $ udp-sender --min-receivers 1 --full-duplex --pipe 'tar czvf - theDirectory' on the sender and $ udp-receiver --pipe 'tar xzp' and at least on my home network it's 11x faster than tar|nc. There are some caveats[1] about udp not working well everywhere, and…

Just remember to compare checksums afterwards. Preferably a cryptographic hash... UDP is known for not being reliable at all, and that's partly why it's so fast --- the sender doesn't care whether the packets reached the receiver, it just sends as fast as it can.

Well sort of. The sender will in a lot (most) of cases care, its the protocol (UDP) that has no automatic checking, or reporting. This sort of stuff is left up to the programmer.

The power of UDP allows the sender to have more control on things like how often transmissions are are acknowledged (tcp window size), or how to handle delays or errors. There are also some advantages because middle boxes who try to be smart and "make TCP" better for you can't really muck with the UDP packets all that much because the applications own protocol of how to handle UDP packets will not likely be know. This is why QUIC is such a big deal -- as a lot of the type of things a middle box might want to -- and do on TCP today -- muck around with are encrypted.

So I would not say that UDP is fast because it is not reliable, it is fast because it can allow a programmer to exploit the network in a more efficient way than TCP can for a specific type of data being transferred. There are many reliable UDP based protocols that achieve faster speeds than TCP in different situations.

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

#34
post #13

Can it have a little more security please? E.g. longer filename, more difficult to guess. And an encryption option would be nice.

gpg2 --armor --output my-file.tar.gz.gpg -e my-file.tar.gz && curl --upload-file ./my-file.tar.gz.gpg https://transfer.sh

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

#37

Personally I've been using magic wormhole lately. It's p2p and very easy to use. https://github.com/warner/magic-wormhole

I love magic wormhole, you give the recipient three words and a number and the file is sent peer-to-peer. No messing about with routing or anything.

How is it for getting around weird networks (double NAT, etc)?

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

#39
post #23
post #16

Of course it's written in Go. It's amazing to see the language embraced that much for server side apps.

Static binaries are magic :)

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

Post reply on HN