On Fri, Sep 8, 2017, at 05:05, Remko Tronçon wrote:
> - Provide a hash of the contents in the , such that the server
> can
> make decisions on upload slot response based on the hash (e.g. give a
> response that this file has already been uploaded).
I like this idea.
> - The ability to omit the
> Clearly, benefits, but I do wonder what can of worms this opens with
> regards to confidentiality. "Wait, someone else uploaded this?"
>
I agree you need to be careful to leak information here, and e.g. only do
this if it was the same user that uploaded it.
Maybe there are other reasons for
Clearly, benefits, but I do wonder what can of worms this opens with
regards to confidentiality. "Wait, someone else uploaded this?"
There is also talks about being able to update content (which I personally
dislike) - but your proposal adds quite a bit of complexity there too.
>From a storage
Hi,
A server may want to provide optimized write-once storage of files that
stores data based on hashes of file contents (such that identical files are
only stored once, and that filenames are opaque). In this light, I was
wondering whether the following extensions to XEP-0363 would make sense:
