Replying to Avatar hzrd149

nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn do you have an documentation on how your WoT score works in coracle? I've built an easy way for loading the WoT in applesauce and Id like to use the same scoring system as you've used in coracle in noStrudel

https://hzrd149.github.io/applesauce/examples/#loader/social-graph

GrapeRank is a more sophisticated WoT algo and extensible library than any client is currently using.

Why do we need sophistication, when good enough is always better? Simply because bots and bad actors will always find ways around “hard coded” WoT parameters … whereas individually configured WoT filters shared peer to peer across clients will always be the best performer.

nostr:nevent1qqswfr8nn3w34eu45u5dqhy9cvyg5kh9pwap7s0zc7aeh4mwct3yxzszyr0k07d8usgj2azuheavl0wdqd530qxxg00hhtts7hfppredflpqqqcyqqqqqqgpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxge27qs9

Reply to this note

Please Login to reply.

Discussion

what events does the graperank take? because thats the limitation on the client side. I can only reasonably afford to fetch the kind:3 follows (and maybe mutes) out to 2 levels (friends on friends). any more and I'm overloading the clients network

“Out of the box” with no config or plugins, GrapeRank ingests follows 6 levels deep to map the network, and interprets these plus mutes and reports for the calculator. It does this server side. Performance would be greatly improved with addition of a cache, which is one benefit of running server side. Calculated scores, from the context of any npub as “observer”, are saved and retrievable at any time. Adding additional interpreters is dead simple…

https://github.com/Pretty-Good-Freedom-Tech/graperank-nodejs/blob/main/packages/ptotocols-nostr/index.ts