Implement new cached metadata system

[stv0g]

We currently use S3 object tags to store some metadata information about each upload.

This works well for most use-cases, however has the disadvantage that the object tags are not easily modifiable.
Or flat out not supported by some cloud hosters (Wasabi).

Some planned features require that we can modify upload metadata (#10, #11).
Hence, I've thought about moving the metadata to a dedicated S3 object.
There is still the disadvantage, that S3 does not really support atomic operations on objects so we still have a hard time tracking download numbers (e.g. any sort of counter). But I already have an idea of implementing some sort of local or distributed (Redis) caching layer in front of those metadata objects which could solve this.

[mrg358]

I just tested out Gos3, so dropping my results.

• AWS works perfectly, no issue.
• Contabo S3 (ceph) results in error "Upload failed: Final checksum mismatch", upload is completed though. On second attempt to upload the same file, it completes without error.
• Garage (selfhosted S3) sadly doesn't work b/c of the missing ObjectTagging API.

I will keep using AWS, but it would be so nice to have broader S3 compatibility.
Very nice app indeed. Thank you for your work!

[literon36]

ContaboS3 (ceph) results in error "Upload failed: Final checksum mismatch", upload is completed though. On second attempt to upload the same file, it completes without error.

this also now happens at the demo instance https://gose.0l.de ... (@stv0g)
I've tried multiple browsers & devices so it should not just be a me-issue.

[stv0g]

Thanks for the input. I am currently running a bit low on resources since I am occupied with my other projects. But contributions in the direction of a new metadata system are very welcome :)