I see both as closely related in that you want to utilize a reference to the previous npub. I know I might be going off on a tangent, but I can see cases where you might want to preserve an identity over multiple key rotations. Should I consider that a completely separate topic?
Read the specification at:
https://github.com/braydonf/nips/blob/beaa4f6971c313612ff5c4c1a0d9d30ecd4908d3/xx.md
Implementation of two new events:
https://github.com/braydonf/go-nostr/tree/d7e124ea994ffa4c17f6561c15bf81deb355b353/nipxx
Pull request for the NIP:
https://github.com/nostr-protocol/nips/pull/1452
Seeking feedback and comments!
I like your proposal. I have been thinking about this a lot lately as well.
Do you think it’s possible to treat this as a sort of password reset? The phrase is not ideal, but it’s descriptive. Users sometimes have a hard time with any sort of secret keeping. In that case, I would imagine they would appreciate it, if the chain of keys remained and was linked as one identity. So the revoked keys remain read-only, as you already have planned, but some relays might opt to keep the events and clients might include them as part of the profile/history of a user and have that as a feature.
Does nostr have any inherent intellectual property or licensing assumptions for the published content?
#askNostr
Look for places and experiences that inspire awe, like in enormous churches, undisturbed nature, music. Feel the feeling and stop to absorb it whenever possible. This is as close as you can get to the holy spirit.
Then consider your relationship to death. Face your mortality. A near death experience or psychedelics might help but are not required. Then read the Christ’s passion and absorb his choices. When you feel in awe of him, you will have found your destination. You will likely feel awe at being alive and it’s as if he’s with you always.
I think reputation and trust go hand in hand. I like the web of trust concepts, where global trust scores don’t mean as much. We’ve found in the last few years that we vary in major ways by how much each of us trust public authority figures with established credentials or various conspiracy theorists. I don’t think it’s a stretch to find two people who sort a given list in exactly opposite directions.
People are also incredibly ingenious about gaming reputation systems. If given enough time we tend to produce a situation where everyone is suspect and we just end up with zero reputation all round, then resort to buying standing and pretend it’s meritocratic.
We should try to avoid the trap of social scores and any scoring authority, even in algorithmic form.
I don’t have any solutions though, only wishes.
Hundertwasser was always one of my favorites
https://en.wikipedia.org/wiki/List_of_buildings_by_Friedensreich_Hundertwasser
Look for the feeling and attitude of being a team. From your description it doesn’t seem like it. Your life with a partner will require some adjustment from the solo play and either one of you should not be making all the sacrifices.
Additionally, kids are amazing, but they will expose all your weaknesses in sometimes heartbreaking ways. Try to aim for ‘oh dear, how do we handle this’ and not ‘whose fault is this mess’. Consider other situations as signposts.
I’m aware. But it’s and idea I would like explored and debated, not simply dismissed on principle.
For the unique static identifier linked to a permanent record on a distributed ledger that you own.
It's a safety net. If your nsec is compromised you would want a way to rotate the keys that is not accessible simply by way of having the nsec in hand. If all you require is nostr events, then the bad actor that grabbed your keys could post these same events in your name and permanently lock you out.
It is also service-agnostic and nostr is not the only reason you might use this, just currently the most obvious one.
I’m writing it down here for now: https://github.com/pubkeychain/pkc-protocol
Do you have recommendations where to share this for some feedback?
I know how to do this in a self sovereign way. It basically gives you a ‘reset pass’ flow as well. It would require a few things though, which I can only describe atm and not yet code into existence.
Wow, I was spectacularly unclear 🙈 I meant to say that the static identifier can as well be a satoshi name even if it’s a mostly random mix of letters and the websites and users can then name themselves whatever they want.
In the end it’s possible that the names don’t even matter. For the lookup to work you need a static identifier to which you can associate new ips and new certs. Maybe we can live without the global naming, since we use search engines, social media posts, adds, and qr codes to get where we want to go.
My main focus has been on providing a self sovereign failsafe for lost nostr keys, and my reason for using the ord name instead or number was because it’s shorter. Readability of handles didn’t matter to me as much. I consider it more in the sense of a ‘telephone number’ made up with letters, for which you could maintain a personal ‘phonebook’ and just name things what you want for your reference, but you never need to look at the ‘phone number’ to get to the person or website you want.
I see the value in naming though and in vanity names. I don’t expect the ord names to become suddenly popular and the availability of names people actually want is a real problem. But I absolutely don’t want to introduce a third party authority into it. That’s a hard pass.
First, thank you 😊
It touches on both, depending on the service you plug it into. I’ll try to describe what I mean.
The handle or global namespace is the satoshi name, for instance the satoshi with ord number 1953186218210489 has a name of ‘aaaaaaaaaaa’.
For nostr, you could save the sat name to your profile and after anyone plugging that satoshi name into search could retrieve all history of all pubkeys contained in the inscriptions of that satoshi and it would all be your content. There are also ways to make sure your pubkeys aren’t appropriated by others.
I can also imagine a service that would handle websites. Dns basically does cert and ip lookup. If you extend the inscription and provide the ip address beside the pubkey, which can be used to verify that the server holds the private key, I can imagine a legit request can be made to get the website data.
Does that make sense?
I have something like this thought out and am in the middle of trying to write out a protocol description. It ticks your boxes, except possibly the last one, since that wasn’t my main focus. Can I ask for your comment once I get over myself and actually publish my idea?
Where I’m from, when millennials mention they don’t expect to ever get any pension from their mandatory payemnts into the system, the older generations mostly agree that it doesn’t look great, but their answer is that we now have this extra gov-run fund where you can invest additional money into your own retirement with a tiny tax deduction incentive. And I ask if they have ever looked up their portfolio and they look at me funny when I say why would I pay into a fund that will buy local government and government-owned businesses’ bonds with this money and tell me it’s all taken care of. It’s a great plan to distribute government debt, but not a great retirement plan. That part hasn’t sunk in yet.