brew install gpg
gpg -ac < file.unencrypted | curl http://transfer.sh/file.encrypted -T -
curl https://transfer.sh/1nKXr/file.encrypted | gpg -ad
transfer file.txt | pbcopy
transfer file.txt | xclip
rsync -P foobar.png personal.sircmpwn.com:/var/html/
# "hey dude, go download http://personal.sircmpwn.com/foobar.png"
No pun detected ;)
$ cloudapp -d myfile.pdf # upload the file and copy the link in your clipboard
It will probably be around for 5 years, but is not undergoing active development, and it was a side project I worked on for funsies (I may come back to it one day, and it's kind of a leave-it-be project, especially without 100s of users).
Please refer to the other ones for a serious (or at least more well thought out) solution.
$ transfer < ./foo
$ transfer acH39gew > ./foo
curl -T ./filename transfer.sh
A better approach than blanket allowing of hotlinking is to whitelist certain user agents (curl, wget) and only allow those to directly download the file, and to present landing pages detailing the file and its contents to everyone else. It's been on my list of things to implement in my own sharing site.
...Based on some words I see on that page, I think they will anticipate abuse and roll with the punches.
ex1: Upload a file to http://transfer.sh
$./pt.py -u /home/something/file1
$./pt.py -u /home/something/file1 /home/something/file2 /home/something/file3
$./pt.py -d https://transfer.sh/19Xwp/file1 https://transfer.sh/1fn4k/file2
Download ./file1 done.
Download ./file2 done.
$./pt.py -d https://transfer.sh/19Xwp/file1 https://transfer.sh/1fn4k/file2 -w /home/user/
Download /home/user/file1 done.
Download /home/user/file2 done.
[/] $ ls -la / | curl -F 'paste=<-' http://fh.tl/
Your paste has been saved!
Share this URL:
ls -la | curl --upload-file - https://transfer.sh/bla.txt
scp "$1" "$SERVER:$LOCATION"
echo "$BASE_URL/$1" | xclip -i