Consider supporting multiple versions of metadata

[tpetricek]

... when inserting a new version of a snippet. Currently, we just overwrite the old ones.

[kunjee17]

@tpetricek what is status of #44 ? Because we can use default functionality database to version system for documents(snippets.).

Like storing things as events (JSON) for every edit. So, that way it will be inline with out current structure.

[tpetricek]

I would ideally like to be able to store things in simple blob storage as one alternative. But we could definitely store edits as events, that sounds sensible no matter how we store it!

[kunjee17]

@tpetricek so, we can try one thing. We don't change current storing scenario but try changing what we are storing (or way we are storing) and store metadata with the data. Sounds good?

[kunjee17]

@tpetricek I m little bit tied up with some other project of mine. So, may be can't give more time to this. I will try to get back this as soon as I got some time. Else have to open up for others to grab.

Sorry :(.

[Thorium]

Currently when updating it seems that:

1. It keeps the author as previous version.
2. It resets the likes to zero.
3. The timestamp resets to current date.