Users get their own folder

[flleeppyy]

Users get their own folder

[BobbyWibowo]

Unfortunately, that'll require quite a bit of under-the-hood refactoring to get that to work as expected
Since the initial design philosophy, since the very beginning, is just to simply store them as random identifiers (pomf-like)

I personally do not have any need for that type of storage scheme, so sorry about that

Alternatively, you can consider serving files with node, and then enabling setContentDisposition in config file
Files will still be stored as their random identifiers, but upon download, browsers will automatically prompt/save the files according to their original names (wget and such need to enable an option flag to instruct them to follow the Content-Disposition header)

Serving files with node won't be as blazing fast as using Nginx directly, but that should only be obvious on very heavy traffic