@hzrd149 and @hodlbod, the WoT coracle has a few issues, that will become more and more apparent as nostr grows: 1. each follows/mute count 1. This doesn't consider that there are people that follow 5k others, while most are more picky, nor considers the reputation of the one following. These nuances are reflected by the pagerank formula for instance https://en.wikipedia.org/wiki/PageRank. The contribute of one's follows are proportional to its pagerank and inversely proportional to the size of the follow-list. This is true both for global or personalized pagerank. image 2. a users has only information on the two-hop network around him. This consists of an average of ~50k people, which is fine for now because the network is small, but won't scale when nostr is at 10M+ users. Vertex abstracts away all of these complexities, and gives simple to use end-points for many common operations like: - sorting replies, comments, zaps... - verify reputation of a target npub - get recommendations I am more than happy to have a chat about how give access to these tools guys, just let me know

Replies (4)

Niel Liesmons's avatar
Niel Liesmons 7 months ago
@hzrd149 just convinced to stop using the Follow concept entirely, lol. Very curious how pageranking will be done in a more Community centered layer of Nostr, with atomic Label/Badge events.
I agree with your first point, valuing each follow/mute should take into account how many users the user is following. I think ill try to learn the math behind page rank and see if it works any better for me For 2. I agree this does not scale but I'm trying to find a simple enough solution that a pure (no server) nostr client can implement that will be the most effective. Once I figure out how to implement the "simple" self sovereign method I would love to see how this could be off loaded to a third party server (or even a personal server on a Umbrel) But for my use case in noStrudel I need the "WoT" to do two things: 1. Sort pubkeys by "rank" (find the real hodlbod test) 2. Filter out new, on-off spam accounts The effectiveness of these things will vary based on if the user is using a locally calculated WoT or a remote service, but I think thats fine