That's a nice truck you got there

Chris Potter Trio at the Atheneum Music and Arts Library. A small intimate venue in LaJolla #SanDiego. Just killin’. #jazz #livemusic

Camel meatballs.

#foodstr

Yeah, that the idea. The trick is the ordering of npubs so that (n+1) npub can announce that (n) npub is no longer valid. Similarly, someone can determine which events were valid and at which point they are invalid. Likely will require an open timestamp.

Not sure. We could do something similar to hkd with xpub, but I think the way to go is to publish events that point to the next valid npub. The trick is absolute ordering, so that if the original npub is compromised it can’t trick you to a bogus new npub.

I am pretty sure there is a simple model underneath it all. Just haven’t figure it out yet. I think it’s something like generating a new npub, publish a kind xxxx event that this is the next npub.

Ok, i guess its time for me to read Mandibles, since i keep seeing it mentioned here on nostr. I looked it up, by Lionel Shriver. Is that the right one? #asknostr

Once again, I am becoming more confident that #nostr and its signed event model is the right way to go. This time around, the model has helped to clarify the distinction between #identifier and #identity.

We’ve all been guilty of using these terms interchangeably, if not as equivalent. I often refer to my npub as my ‘identity’, the shorthand way of referring to my ‘identifier’. I also think of them as being the same, with the knowledge that my ‘identity’ actually exists outside of any one system.

Now with #nostr, the distinction has been clarified: my ‘identifier’ is my npub (straightforward enough) however my ‘identity’ is my npub PLUS a set of events of events signed by my npub.

At its most rudimentary level, my identity is my npub + a kind 0 event with metadata. What is interesting, my identity can change over time if I sign and publish a new kind 0 event.

As well, my identity might look different to different people - the best example is a signed nip04 event that is encrypted and readable by only one other npub. My identity is different to that one npub as it would be to another npub that does not have access to that nip04 message.

This line of thinking about ‘identity’ opens up a way to rotate npubs (use a different identifier), yet keep the same ‘identity’. A possible approach is to create a new npub that signed in a way to be used next in the chain if the old npub is compromised.

Anyway, just some thoughts on the distinction between ‘identifier’ and ‘identity’ - it’s the addition of signed events.

#jazz #music

Herbie Hancock

“Why would I spend bitcoin?”

— person who spends unrealized-sats every day in the form of fiat