Parker is right in the sense that we still don't have key migration process.

Reply to this note

Please Login to reply.

Discussion

Web of trust will be the ultimate solution for hacked keys. My WoT is how I’ll know that Alice’s pk1 was hacked as of T1, that she’s using new pk2 as of T2, and to treat her content accordingly.

Nostr is where true WoT will be launched. We need to get that built first. Key migration will fall into place after.

What's interesting to me is that there are already solutions out there, but the problem is the same as with post editing... you have it in Amethyst where nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctcscpyug implemented it... and it doesn't work anywhere else...

where can I understand better what key migration is and does nostr:npub1j8y6tcdfw3q3f3h794s6un0gyc5742s0k5h5s2yqj0r70cpklqeqjavrvg?

and what does getting the WoT built look like, nostr:npub1u5njm6g5h5cpw4wy8xugu62e5s7f6fnysv0sj0z3a8rengt2zqhsxrldq3?

What I envision is that we will see an evolution of personalized WoT relays into a sophisticated tool that will keep track of our webs of trust and use them to curate all of our content. I say “webs” plural bc there are different ways to calculate it, different ways to use it, an effectively unlimited number of categories of “trust.” For whatever topic you’re interested in, your personal WoT relay will tell you who are the most trustworthy or knowledgeable, even if those people are not already one or two hops away from you on the social graph.

Once that’s done, key rotation will be only one of a thousand problems that we will address with it.

🍇 🧠 ⚡️ 💜

From a more technical perspective:

There are different ways that a personalized WoT relay can define WoT. One way, probably the simplest way, is your WoT = your follows + their follows. That method is great at getting rid of spam, but throws out a lot of the baby with the bathwater. Newcomers to nostr in particular may be underserved by this method of calculating WoT.

There are ways to tweak the above method for calculation of WoT, but I think the next generation personalized WoT relays will implement centralized algorithms like PageRank, which is what put Google on the map in 1998. PageRank does a better job at sorting the wheat from the chaff than the simple “follows of follows.” This will be especially important for newcomers to nostr, for two reasons: first, newcomers will have only a few followers at first, which means they’re more likely to be excluded, and for a longer period of time, using the follows of follows method. Second: newcomers will have only a few follows at first, which means their follows of follows may be too restrictive in the beginning. Many of them may quit nostr before discovering all that it has to offer.

The downsides of PageRank are that it is not contextual and not suitable for using as a weight when doing weighted averages or weighted sums. I use the term GrapeRank to refer to centrality algorithms that address those two shortcomings. They’ll require nonlinear equations (as opposed to PageRank which is linear) which means extra compute, but they’ll be powerful and versatile and I think they’ll be unexpectedly awesome. It’s just a matter of putting in the work and building them out.

🍇 🧠 ⚡️ 💜

you can ask me about it at the next Shaman gathering

I hope to understand it before that, unless one is happening by next week ;) We live in accelerating time...

By solutions are you referring to Vitor’s NIP-85 WoT solution? I wasn’t aware he had implemented it in Amethyst yet, but I def want to see that happen, and I want to see other clients do it too! nostr:npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxy and I and maybe others by now are generating WoT scores using kind 3038x notes, as per his NIP-85.

Or are you talking about a key rotation solution?

btw here is Vitor’s WoT NIP, Trusted Assertions, and its pull request discussion:

https://github.com/vitorpamplona/nips/blob/user-summaries/85.md

https://github.com/nostr-protocol/nips/pull/1534