Relays. You know... The backbone of the nostr protocol. Not all relays run the same software. There are many different implementations.
Everyone is focused on clients. Without relays, none of them work.
I don't mean to come off blunt. If you're really unaware of how relays work Id be happy to go more in depth. I can point out the most prevelant implementations if it helps.
Replies (4)
I'd love to learn more about relay internals btw 👀
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?
I was mostly referring to projects that create user experiences for creating relays rather than not knowing what the R in nostr means
I still have a misunderstanding. Coding creates relays. Just like clients. They all have some level of configuration. Relay.tools is the only relay "creator" I'm aware of and my original post was not to point out all projects that do this. It would be to point out all different implementations of of a nostr relay.
