I am a big fan of FileTea’s approach to transferring files, where they are streamed from browser to browser, without registration and without being stored on some central server, and where closing the browser tab reliably cleans up the transfer. But I wanted something that works from the command line, so I created a small tool called share-file that will use SSH port forwarding to serve the files from a local, embedded web server at a publicly available port, as shown in these screenshots:
It works without additional dependencies (but better with python-magic installed) and requires a publicly available SSH server configured with GatewayPorts clientspecified. For more details, see the README, and to try it out, simply fetch it with git clone git://git.nomeata.de/share-file.git.
I did not know about filetea. I am the author of Fipes  a web application that seems to solve the problem in the exact same way.
I think there is no technical difficulties to solve the 949 problem (however we can argue on the definition of "fixing" here).
We need to make people more aware of the fact that free software solutions exist.
Anyway, congrats for this simple solution, using ssh here is quite clever :)
I had a similar idea for Emails, but never got around to actually implement it. I thought it would be a good idea to strip of binary attachments, put them on a webserver and replace them with a link to the file. To avoid potential security risks, the link to the file should be a shaXXX sum. Of course, if someone wanted real security, they should encrypt their files.
I think your solution is a step to that direction. It could probably be easily used as a postfix filter.
How do you generate your links (the AYLD.. part?)
Oh my, I completely forgot about this, sorry.
Several solutions for obsolete files come to my mind.
- Provide the sender with a deletion link
- Provide the receiver with a deletion link
- Provide both, sender & receiver, with a deletion link; do reference counting for multiple deletion links
- Automatically delete the file after X amount of time
- If the email is kept on the same server (e.g. by imap) keep a database of email/file references and delete the file when the email is deleted
Would be fun to implement something like this, if I had the time. :)