Brainstorm currently uses #neo4j to track a graph with NostrUser nodes and follows, mutes, and reports as relationship types. This schema will gradually become more complex (add NostrRelay nodes, NostrEvent nodes, various other relationship types), and in its final form it will be a continuously-updating, personalized nostr knowledge graph that your WoT helps you to manage. Native graph databases with sophisticated query languages like cypher are designed for exactly this sort of thing.
I recently joined nostr:npub1healthsx3swcgtknff7zwpg8aj2q7h49zecul5rz490f6z2zp59qnfvp8p and we are putting the finishing touches on plans for a WoT Hackathon. We’re looking to support anything that’s open source that advances nostr towards a healthy ecosystem of personalized trust metrics that are calculated by service providers (which you can do yourself, or pay a third party) and then made available to clients. Graph database nostr relays will be very useful for this, and we’d love to see multiple implementations. So if you’re interested in contributing to one, consider doing it as part of the WoTathon. We’ll be thinking of how we can facilitate individuals with common interests finding each other to form teams for projects like this.
nostr:npub10mtatsat7ph6rsq0w8u8npt8d86x4jfr2nqjnvld2439q6f8ugqq0x27hf is also building a neo4j nostr relay and you should follow his work.
nostr:npub1mgvwnpsqgrem7jfcwm7pdvdfz2h95mm04r23t8pau2uzxwsdnpgs0gpdjc has used neo4j for DVMDash — Dustin are you still working with neo4j?
nostr:npub1057d3g2zw9w4ns8fq43yka3per9s2z9zmp4ryncgqqvv6e42tjrqnrxgd7 has worked with GUN, another graph database, and has expressed interest in making a GUN nostr relay.
Anyone else working on or interested in using graph databases within nostr?
#wotathon