51–60 of 80 posts
This will be abused for hosting questionable things in no time, if it's not already.
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.
I wish the URL could include a hash of the content so it could be used for verification for uploading and downloading the files. It could be handy for error checking and security checks.
$ transfer ./foo
This will be abused for hosting questionable things in no time, if it's not already.
...Based on some words I see on that page, I think they will anticipate abuse and roll with the punches.
How do you intend to make money?
curl -T ./filename transfer.shMy usual procedure goes something like this: rsync -P foobar.png personal.sircmpwn.com:/var/html/ # "hey dude, go download http://personal.sircmpwn.com/foobar.png"
My usual procedure goes something like this: rsync -P foobar.png personal.sircmpwn.com:/var/html/ # "hey dude, go download http://personal.sircmpwn.com/foobar.png"
I do this too, but I find it annoying not knowing if the file has been received and when it's safe for me to delete it.
Nice, finally hassle free service. No registration, proprietary clients etc...