Earlier quoted context omitted.
Just to reiterate what dchest said, you should never use MD5 anymore, even if you do intent to hash something. MD5 is is broken and should not be used for anything anymore.
What about Gravatar?
Show HN: YouTransfer – Self-hosted file sharing
31–40 of 77 posts
Re: Show HN: YouTransfer – Self-hosted file sharing
#32Much appreciated, added to my list o' useful things.
Re: Show HN: YouTransfer – Self-hosted file sharing
#33Oh, thank goodness. I was looking for a solution like this less than a month ago and couldn't find ANYTHING usable. Much appreciated, added to my list o' useful things.
Re: Show HN: YouTransfer – Self-hosted file sharing
#34Re: Show HN: YouTransfer – Self-hosted file sharing
#35Earlier quoted context omitted.
Any suggestions?
Not San Francisco not San Francisco not San Francisco ;)
How about Proxima Nova? (http://www.marksimonson.com/fonts/view/proxima-nova)
Re: Show HN: YouTransfer – Self-hosted file sharing
#36https://github.com/warner/magic-wormhole
It's file sending from 1995.
Re: Show HN: YouTransfer – Self-hosted file sharing
#37Re: Show HN: YouTransfer – Self-hosted file sharing
#38Congrats on the project. Without loading and looking myself, how are the file accessible on the server? I asked because I'd like to have clients use this to send ME files only. Is that an option?
Using the default settings, you would get something like "./uploads/0b692a00635682fabc78b6a50655242c.binary" in the application directory.
I've already has plans on making it possible to change the interface, for instance not allowing direct download from the homepage. I could ament this with the feature to send email notifications to the system administrator upon successful file transfer. The combination of both would allow you to use YouTransfer.io as a public drop box for files. Does this sound about right to you?
Re: Show HN: YouTransfer – Self-hosted file sharing
#39Congrats on the project. Without loading and looking myself, how are the file accessible on the server? I asked because I'd like to have clients use this to send ME files only. Is that an option?
Currently, the files are stored as a flat file list on the file system using their randomly generated token to create a [token].json and [token].binary file. The JSON file contains meta information, the .binary file is the actual file. Using the default settings, you would get something like "./uploads/0b692a00635682fabc78b6a50655242c.binary" in the application directory. I've already has plans on making it possible…