What would you like to know? The concept is simple so the implementation is very open to do it a million ways. They are just web socket servers that interpret events as defined by the protocol. How you handle them is up to the relay. I mean you have to handle them a certain way as defined by the protocol but I mean how you handle storing events or responding to requests is all free game. Grain for instance is inple in go and uses mongodb as a database. Strfry is in C and uses LMD. Etc.
What would you like to know more about?
Login to reply
Replies (4)
strfy is C++. Big difference XD
Whoops, yep. Not super firmiliar. Big difference. Going off memory. Maybe I was thinking of Bitcoin.
Its not a specific question but related to this thread:
Maybe if embeddings can be made portable enough, they can also be passed around nostr in a decentralized way, where clients and relays would be able to leverage note searching. Kind 1 seems like a big ask, because your essentially trying to classify and search through all possible conversations and context is usually temporal.
More slowly moving kinds, where context is contained within the note, or surrounding notes on a relay would be interesting to organize around. But what about paragraphs? If so, maybe binary embeddings on relays could be a thing to help organize and find related notes.
Can anyone teach me how to do this? https://emschwartz.me/binary-vector-embeddings-are-so-cool/
There is so much jargon about this stuff I don't even know where to start.
Basically I want to do what https://scour.ing/ is doing, but with Nostr notes/articles only, and expose all of it through custom feeds on a relay like wss://algo.utxo.one/ -- or if someone else knows how to do it, please do it, or talk to me, or both.
Also I don't want to pay a dime to any third-party service, and I don't want to have to use any super computer with GPUs.
Thank you very much.
View quoted note →
Something about a vector binary embedding of an entire relays content to perhaps make searching a compressed relays content extremely efficient and perhaps you could embed all of the content across the entire protocol. Then it could be redundant and spread everywhere and all nostr content may no longer need to be fragmented across relays but aggregated with the embedding and globally distributed across all relays. Sounds really complex though.