LynAlden on Nostr: I have an #asknostr about Nostr. In a client, we select which relays to connect to. ...
I have an #asknostr about Nostr.
In a client, we select which relays to connect to. Is that list of relays that we have chosen to connect to stored on the client side, or does that list of relays become an event that gets sent to relays as well?
I assumed the latter, that my relay list is published to relays, because if I spin up my keys in a new client it seems to have the same relay connections. But then if I change the relays there in that new client, it doesn’t seem to change the relays on my other prior clients. I assume this is because of the basic Nostr fact that there is no global state and thus relays can have different information about the same user/keypair. Or is some of the relay network connection list stored locally on the client as well?
I guess a broader question is, what types of Nostr information are persistently stored locally on a client?
In a client, we select which relays to connect to. Is that list of relays that we have chosen to connect to stored on the client side, or does that list of relays become an event that gets sent to relays as well?
I assumed the latter, that my relay list is published to relays, because if I spin up my keys in a new client it seems to have the same relay connections. But then if I change the relays there in that new client, it doesn’t seem to change the relays on my other prior clients. I assume this is because of the basic Nostr fact that there is no global state and thus relays can have different information about the same user/keypair. Or is some of the relay network connection list stored locally on the client as well?
I guess a broader question is, what types of Nostr information are persistently stored locally on a client?