nusa / Nusa is on Nostr

"8d2debe951bd7070b6506d29971d16cf7a9da7c52646bb38948fb62c1924c7f692186a3e57529e52b2eebccd07db4cd89591aec77068d78ff153dd2c2a13c3cc"

Last Notes

2024-09-22 12:03:39

- reply

Is this in line with what you are saying? I’m really curious, but don’t quite know how to discuss this.
https://github.com/pubkeychain/pkc-protocol

2024-08-31 10:32:42

- reply

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.

2024-08-25 23:17:31

- reply

I’m aware. But it’s and idea I would like explored and debated, not simply dismissed on principle.

2024-08-25 19:52:24

- reply

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.

2024-08-25 12:59:30

- reply

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?

2024-08-24 17:50:48

- reply

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.

2024-08-24 10:45:43

- reply

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.

2024-08-24 09:34:58

- reply

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.

2024-08-23 21:56:09

- reply

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.

2024-08-23 20:15:49

- reply

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?

2024-08-23 16:43:12

- reply

Here goes…
https://github.com/pubkeychain/pkc-protocol

2024-08-19 22:07:15

- reply

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?

2024-08-18 10:42:07

- reply

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.

2024-08-09 13:11:08

A storm with unusually dense lightning broke directly over our neighborhood the other night. We have a home office set up with quite an elaborate network and a lot of electronics. We had multiple surge protections in place for the power, but the surge came in over the coax data cable and fried our router and switch. 🙈