Feature: read nsec from an encrypted qrcode about nos2x HOT 6 OPEN

This is cool, but we need it to be standardized so it works with all other Nostr clients. There are already some clients doing nsec encryption, and would be nice to get everybody to use the same algorithm before we implement anything.

from nos2x.

I don't like that at all. Having parameters in the encryption thing just forces everybody to implement all possible parameters.

from nos2x.

I guess yes.

I had forgotten about this issue.

from nos2x.

nice, in private qrcode I'm using an encode that allows me to parameterize which algorithm is being used:

encrypted:[algorithm]?[args];[cypher]

encrypted: identify the string as encrypted encode
algorithm: algorithm name
args: algorithm arguments
cypher: cypher, encrypted content

Example

encrypted:aes?iv=249704f119c3d09e4e0fb3b6a275e519;U2FsdGVkX1/mxOv5WpmRGHXZouip6GOw+P+Jdks6c1Z/uMfwBl7Me+dzJjioF72z9E+bKY/GlcL8HlWnWrs7fTlqVvzmsC3b2dm+JfL2rTH+60dNlk6PJ+41pLRDWA/l

See if this idea can contribute to this standardization

from nos2x.

Nostr can support a single one algorithm with standardized parameters, this encode helps, if the future demands it, to add new algorithms and parameters keeping backwards compatibility.

My suggestion of encrypted encode is inspired by the data url specification (the parameters idea I got from NIP4):

data:[<mediatype>][;base64],<data>
data:text/plain,Hello%20World

As I said before, I am available to implement this feature to your plugin if you wish, following your decisions.

from nos2x.

So, NIP49 implementation is the standardized way to solves this?

from nos2x.