Improved security

[fryorcraken]

• Notes are fully encrypted using Waku Message version 1 (no metadata leak)
• Notes are always encrypted, key is part of the URL
• Using standard uuid v4 from browser API to generate ID
• upgraded deps to fix a bug

[weboko]

Thank you for showing it @fryorcraken!
Now I understand what you meant by implying that we can fully encrypt messages.
So that it works in a way that consumer reads only messages that it is able to decrypt.

I agree that such way suits note app best.

Additionally I think there are still applications that should have only parts of messages being encrypted so I propose to keep the methods exposed in @waku/message-encryption.

[fryorcraken]

Additionally I think there are still applications that should have only parts of messages being encrypted so I propose to keep the methods exposed in @waku/message-encryption.

I don't really agree with that. It is best if all application encrypt their messages one way or another to prevent any metadata leak.

[weboko]

It is best if all application encrypt their messages one way or another

this not necessarily needed, for example blockchain has everything public and it turns out as a feature - allowing everyone using it as a common DB layer so that anyone can build messages on top of public contracts

ok, we can disagree on this - it is an approach for building app which we are not enforcing
if you insist we can prevent from showcasing it in examples / lab repos

but, I do have another point and that is that - if project is using Waku - then it might need encryption library not only for Waku but some other stuff - example of scenario is when Waku is complementary layer of communication and not main one

in that case it is useful to provide basic encryption in order to decrease amount of packages used by a given project