So, clients can't just manipulate your relay lists without your authorization. It needs a signature from your private key. Now, depending on how you a...
So, clients can't just manipulate your relay lists without your authorization. It needs a signature from your private key. Now, depending on how you are logging into those clients, they may have more or less ability to obtain that signature, and you may have manually granted authorization for a request to update your relays without really looking at what the request was asking.
You are absolutely right that Luminostr is not terribly useful for the average user. It takes a little bit of knowledge of kind numbers. Here are the main ones I use Luminostr to look up:
10002 - Already discussed, this is your main relay list for public outbox (write) and inbox (read) relays. If a relay does not have a "read" or "write" tag after it on the list, then it is acting as BOTH outbox and inbox.
10050 - This is your DM relay list, where you can receive encrypted private messages. Ideally, it should use relays that will only let YOU fetch messages that are addressed to you, using a feature called AUTH.
3 - This is your follow list, and shows every npub you publicly follow. If a client can't find your existing follow list, then it will create a new one the next time you follow someone from that client. Being able to dig up an old follow list to restore them is very handy indeed if you like to test out various clients.
10000 - This is your mute list. Similar to the follow list, these can get nuked pretty easily and for similar reasons. Additionally, some clients support private, encrypted mutes, while others don't. If you have muted someone privately on a client that supports them, and then mute someone else on a client that doesn't support private mutes, the private mutes are often lost.
All of these are what are called "replaceable events." This means that relays are supposed to discard old versions of them once they have received a new version, that way you don't have more than one relay list, or more than one follow list, etc. If a client receives more than one version of a replaceable event, it will go with the most recent version. However, because Luminostr pulls from so many relays where old versions of these replaceable events might still be available, I can use it to see a history of edits made. This makes it very useful for diagnosing when a problem with one of these replaceable events occurred and how, and then give instruction on how to fix it.
For instance, I can see that your oldest available relay list was created 6/13/2025 and had 12 relays listed on it, with all of them listed as both outbox and inbox. This tells me you were probably using a client that didn't allow you to select which relays were read and which were write, like Damus or Primal.
Then you edited your relay list on 3/3/2026 to get to the state it was in when I made my previous recommendations. Since you already had a kind 10002, it is unlikely that a client would have automatically created a new one for you, let alone one with that particular setup. It's still somewhat possible, though, since your old relay list was only found on one relay, and if the client you were using on 3/3/2026 could not find that relay list, it may have generated a new one and requested a signature from whatever signer you were using, if you were using a signer at all.
Finally, it looks like you updated your relay list today and you now have 3 outbox relays and 4 inbox relays. Looking much better. Moreover, it looks like you did so using the Ditto client. However, you have not yet updated your DM relay list.
Expand Collapse 
