"... Finally, you can then save data to their account that nobody else can write to:
(...)
When it is stored on disk or sent over the wire, it uses cryptographic signatures (see the video explainer), to secure the account and data without relying upon any trusted servers!
And then when you use GUN to read the data, it automatically verifies and decrypts the data for you:..."
Really means to say that data is always signed and encrypted (presumably, effectively encrypted with authenticated encryption) - and not simply signed?
It's one thing to be able to prove who wrote what, another to be able to read what everyone writes... And the latter isn't usually what you want...
There are a couple properties it automatically encrypts/decrypts (account data when you login), but beyond that you have to tell it what data is private versus public with `SEA.encrypt`.
Thank you for pointing out those docs though, certainly need to be fixed to clarify more (rather than leaving it to the video explainers) - will do that now. Thank you!
"... Finally, you can then save data to their account that nobody else can write to:
(...)
When it is stored on disk or sent over the wire, it uses cryptographic signatures (see the video explainer), to secure the account and data without relying upon any trusted servers!
And then when you use GUN to read the data, it automatically verifies and decrypts the data for you:..."
Really means to say that data is always signed and encrypted (presumably, effectively encrypted with authenticated encryption) - and not simply signed?
It's one thing to be able to prove who wrote what, another to be able to read what everyone writes... And the latter isn't usually what you want...