-
@ Jay
2025-01-29 03:22:55
Yeah, I have it up on github. It requires a neo4j instance running somewhere, and I forked rust-nostr and included it as a submodule in case I want to edit it.
https://github.com/wisehodl/neostr
As of right now, it acts like a client or cache, connecting to my preferred relays and pulling events. It uses python and rust-nostr, but neo4j also provides drivers in Go, which would also be a good fit with existing nostr libraries (go-nostr, eventstore, khatru).
Personally, I'm using this approach because it's in line with the nature of graph-databases. Graph algorithms work best when you have a starting point you expand out of. So I'm avoiding mass-imports of a lot of potentially disconnected data and spam. To get a global view, I want to expand out using mutual-engagement-driven web of trust rather than processing every event on the network. New npubs would have to put in some proof of work engaging with the network to gain ground in this kind of web of trust model, which flips over the platform model where incoming engagement is all that matters.