What are the chances of integrating @Vertex DVMs for spam filtering at the client level? I think it's the best thought out solution. Maybe @Pip the WoT guy can chime in
Login to reply
Replies (1)
@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.
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
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