>>7530
>if so, what format? I was of thinking of .mp4 or .webm but then there is problem with not preserving "original" or potentially taking too much space
My primitive organizing system based what quality on how important each video was. A very important video would get saved in mkv while lower priority ones I would just select webms and sometimes mp4s of varying resolutions. And podcasts on YT and would just go for lower quality audio and video seperately (and probably stupidly) though I never quite figured out those.

Keep in mind, this was all done to persevere space, as I was paranoid of harddrive crashes, limited resources and life drama my plan was to see how small I could keep the archive. Like a 32 GB or 64 GB flashdrive that would have a broad section of everything. Not sure what resources you are working with but perhaps it would be a good idea to archive just webm or mp4 and only have higher tier back ups if the video is important?

>* Should we include Meta file? (could be packaged with the archive) It could include: time of download, video name, time of release, channel name etc
I would lean toward yes.

>It would be machine-readable so it could be used with potential players/viewers (I still really like the idea of having custom viewers/players one day)
Like a custom browser based player?

>* Structure of the archive - What folders and what put where? I was thinking of:
>* src/ for css/js and src/avatars/ for avatars
>* meta/ for meta file/files
>* raw/ for json comments, video, thumbnail? - I don't know if this should be in src/ (or whatever we'll use for resources) or if there is any benefit in putting it elsewhere
I will think on it... though again, if I suggest something stupid and unworkable.