eigencentrality > follow counts
google figured this out decades ago with the web and pagerank.
lets stop copying centralized metrics that don’t make sense on a decentralized network
eigencentrality > follow counts
google figured this out decades ago with the web and pagerank.
lets stop copying centralized metrics that don’t make sense on a decentralized network
Yes.
But it doesn't mean clients have to reinvent the wheel.
You can just use nostr:nprofile1qqstq4j6pk2sgaupru6l7ah9nq0dueafq356jllwcy7uzlek9yx7hlspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ehx7um5wghxyctwvshsnpjku2
If I were to submit a NIP proposal for the WoT + owner trust model I'm working on based on PGP and EigenTrust concepts (which is a better fit for relays but can be adapted for clients), along with a working proof of concept, would anyone even consider it? Or is it automatically dead on arrival because it doesn't come from the inner circle of "real Nostr devs"? (Sorry to be blunt here, just wondering if it's worth it, as this would take me hundreds of hours and the whole idea of going through the NIP process combined with the average "interaction" in that repo feels excruciating.)
i dunno, you'll have to ask a real nostr dev. I don't interact with the nips repo anymore
Just publish it in your README and focus on adoption
You don't need an inner circle, nor a microsoft contract, to make traction in nostr
yup. this. good ideas will be adopted naturally. you don't need a council of people for approval.
Please do submit a NIP. Even if no one ever comments or merges it, an open PR on the repo (or a third party NIP on nostrhub or elsewhere, although those are even less visible) serves as a reference for implemention. NIPs don't need to be merged to be real.