melvincarvalho on Nostr: Nice thought process, I believe you are on the right track. In nostr your primary ...
Nice thought process, I believe you are on the right track.
In nostr your primary identifier is your public key. It is overloaded to do two things, one is to identify a user, the other is for cryptographic proofs, namely signatures via schnorr.
Your identifier denotes you. Of course, you are not both a key and a person, but that's the trade-off that nostr uses.
Identity is quite a nebulous word, but it's a kind of footprint, around the concept of you. If you really want to get into metaphysics "you" isnt even fully defined, but we know what it means.
In nostr, right now, there is a de-facto 1-1 relationship between your identity and your key. There are exceptions, but it is not the norm. As nostr grows and becomes more useful, it should evolve. It should have evolved a bit by now. More work is needed. #subkeys would be a good start, but we've only explored a fraction of what can be done. One reason is NIP centralization does not lend itself well to new innovation. This can and should be fixed.
There is a good thought process here, but it's a problem as old as time, namely denotation vs connotation. You're not going to get the average user to understand the nuances. Devs need to understand pointers, which is essentially what this is all about. And that's a classicly difficult dev problem. Lots can be fixed, but that's ah opportunity to make nostr much better.
In nostr your primary identifier is your public key. It is overloaded to do two things, one is to identify a user, the other is for cryptographic proofs, namely signatures via schnorr.
Your identifier denotes you. Of course, you are not both a key and a person, but that's the trade-off that nostr uses.
Identity is quite a nebulous word, but it's a kind of footprint, around the concept of you. If you really want to get into metaphysics "you" isnt even fully defined, but we know what it means.
In nostr, right now, there is a de-facto 1-1 relationship between your identity and your key. There are exceptions, but it is not the norm. As nostr grows and becomes more useful, it should evolve. It should have evolved a bit by now. More work is needed. #subkeys would be a good start, but we've only explored a fraction of what can be done. One reason is NIP centralization does not lend itself well to new innovation. This can and should be fixed.
There is a good thought process here, but it's a problem as old as time, namely denotation vs connotation. You're not going to get the average user to understand the nuances. Devs need to understand pointers, which is essentially what this is all about. And that's a classicly difficult dev problem. Lots can be fixed, but that's ah opportunity to make nostr much better.