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.
Discussion
Iād love to see that happen. If you were to use it to calculate personalized trust metrics, that could be a great fit for nostr:nprofile1qqstu7l4mcrgc8vy9mf55lp8q5r7e9q0t6j3vuw06p32jh5ap9pq6zspr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7epadxgās upcoming WoT hackathon!
#wotathon
Also: nostr:nprofile1qqs8a474cw4lqmapcq8hr7res4nknar2ey34fsffk0k42cjsdyn7yqqpz9mhxue69uhkummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctce3f453 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.
