Idea: could we use a SHA1 key as id for images and sounds?

[jonaslu]

Would it help to identify all sounds and images as a "package" with a SHA-1? This way we're not tied to names being unique and we can add more metadata to the samples easily. In the backend we can serve images and sounds with the same key. This would make templating easier?

The sounds and images could be a json-object, example

  { '097d80883f7c5e0f49c1bd24e15942e9ba11f37b': {
    'wav': 'sound/097d80883f7c5e0f49c1bd24e15942e9ba11f37b.wav',
    'length': '10',
    'image': image/097d80883f7c5e0f49c1bd24e15942e9ba11f37b.png',
    'mime-type': 'image/png' }
  }

[jonaslu]

Stats could go into the json object too..

And then we could build a database / metadata admin backend to parse the json and print stats..

TEH POSSIBILITES ARE ENDLESS!!! (Given infinite amount of time...)

[meros]

I have been thinking in these terms as well. But at the same time I'm reluctant to loose the simplicity of simply files in a folder... The stats however should probably change, the format is not very nice.

[jonaslu]

Ok, in a distant future - if we add uploading of files via the front-end maybe this will be necessary since the url:s will probably not be clear what the file is. Or we can add a dialog where the user can name the downloaded file. Let's keep it simple until then...