Oh man.. graph databases are so cool. Why don't we have any relay powered by a graph database yet? Looks like nostr and graph dbs were made for each other. Also, why the hell no database implements string interning by default? What a lost opportunity of speeding up all string queries.

Replies (22)

So much could be done to improve it such as a better semantic search (using AI sentence transformers) or considering how agents can use that to re-organise and strength memories (akin to what we think happens we we are sleeping). What are the details of the hackathon? In person thing?
The goal was to run this for my client when it launches. Setup 5 nodes around the globe. This solved a few issues around backups. Was hoping to also have a minimal offline sync inside my client. This way people could sign events without Internet and it syncs globally when connected.
I'm more than happy to continue working on it. I know theres a few issues I have. One being the websocket for read and writes. Sometimes notes don't display properly on my clients feed. I think its a data structure problem in the code. Reformatting the data to fit into graph. I can play with that. As far as follow data I think that would be possible. The relay does have http search functionality. ws for read/write, http for searching data. The http stuff work better than the ws.
Also: @Jay is working on a neo4j nostr relay in go and has put a lot of thought into overall graph db relays architecture. I think graph db relays could form their own special class of relay and it could be fruitful for a gunDB relay dev and neo4j relay dev to bounce ideas off each other.
โ†‘