manime on Nostr: Independent is a strong word. We’ve been in touch and collaborating the whole time. ...
Independent is a strong word. We’ve been in touch and collaborating the whole time.
The GrapeRank engine I’ve made is intended as a library for other search engines and clients to implement. It has Interpreter, Calculator, and Storage components.
- The Interpreter requests content (like follows, mutes, likes, ect…) from any network (Nostr or others) and normalizes these for calculation, as per existing (and extendable) protocols. It receives configs for this from the engine request.
https://github.com/Pretty-Good-Freedom-Tech/graperank-nodejs/tree/main/src/Interpreter/Nostr
- The Calculator is where the algo lives. At its heart is a ScorecardCalculator class with sum and calculate function for each user or content to be “scored”. Sum collects values from interpreted content and calculate returns the final score.
https://github.com/Pretty-Good-Freedom-Tech/graperank-nodejs/blob/main/src/Calculator/index.ts
- The Storage component can be extended to use any storage backend (including Nostr events for relays, once we settle on a standard schema and NIP proposal). It stores and retrieves calculated lists of users (or content) and list configurations (called worldviews) for quick retrieval.
The “WoT” base level “grapevine” list (of a users entire “not spam or bot” network) takes about 5 minutes to calculate.
As we move forward, “worldviews” configured by users will be able to input their grapevine (or any other) list to create more specific lists that will be able to be dynamically updated.
- most recommended News bots
- Nostr developers
- popular clients
- Nostr artist
- ect…
My Grapevine is an evolving demo of some of this functionality.
https://grapevine.my
The GrapeRank engine I’ve made is intended as a library for other search engines and clients to implement. It has Interpreter, Calculator, and Storage components.
- The Interpreter requests content (like follows, mutes, likes, ect…) from any network (Nostr or others) and normalizes these for calculation, as per existing (and extendable) protocols. It receives configs for this from the engine request.
https://github.com/Pretty-Good-Freedom-Tech/graperank-nodejs/tree/main/src/Interpreter/Nostr
- The Calculator is where the algo lives. At its heart is a ScorecardCalculator class with sum and calculate function for each user or content to be “scored”. Sum collects values from interpreted content and calculate returns the final score.
https://github.com/Pretty-Good-Freedom-Tech/graperank-nodejs/blob/main/src/Calculator/index.ts
- The Storage component can be extended to use any storage backend (including Nostr events for relays, once we settle on a standard schema and NIP proposal). It stores and retrieves calculated lists of users (or content) and list configurations (called worldviews) for quick retrieval.
The “WoT” base level “grapevine” list (of a users entire “not spam or bot” network) takes about 5 minutes to calculate.
As we move forward, “worldviews” configured by users will be able to input their grapevine (or any other) list to create more specific lists that will be able to be dynamically updated.
- most recommended News bots
- Nostr developers
- popular clients
- Nostr artist
- ect…
My Grapevine is an evolving demo of some of this functionality.
https://grapevine.my