Open jamie9090 opened 1 year ago
Doesn't seem like it, but I would love this feature. Even just triggering an update manually.
Manual updates would be amazing. Since users don't have accounts, I think that authenticating (preventing other people from editing your notes) could be difficult, though there are ways around that problem.
I think it would be possible by adding a reusable asymmetric encryption key. The private key can be stored locally and the public key gets stored together with the file. This way the notion of an "account" is still not necessary but it would be possible to securely update files. I would be willing to work on this. @mcndt Do you think this is a good approach or do you suggest another? (e.g API key, ...)
That's certainly an option. Is there a reason for the key to be asymmetric? I think the same can be achieved by the server returning a single-use symmetric key after the first upload, which can be used once to update the content. After updating the content, the server returns a new key.
Asymmetric keys are more compute-intense and could theoretically form an attack vector for a DDOS attack (again, theoretically at least, I think). A symmetric key that we can just compare would be simpler in that regard.
+1 on a feature like this
+1 please
Does the hosted file update if the Obsidian doc changeS?