I enjoyed those, and also enjoyed the linked articles and illustrations. Maybe sharing where I got hung up is easiest to convey what I lack(ed). In the @primal and @nos and @npub1n0st...k6h0 and @Damus clients there’s a single relay list. In @noStrudel on my @npub126nt...e9ll there are two relay lists. Unclear why. This makes me think there’s something I don’t understand about relays and how my client may browse them based on my settings and how I am to find the content and users I would enjoy connecting with if there can be pockets of relays that coalesce but segregate organically. The relays I set in my iOS client are DNS based friendly names, but shouldn’t TOR relays ( like my @npub126nt...e9ll ) be able to be used too? It’s already ws:// over TOR, must I really install a self signed cert to go full wss:// to allow mainstream clients to use it? @noStrudel uses it fine off-LAN over Tor. and about my relay, if I want my relay to respect delete requests or not, store my notes and archive notes of follows, or some other relay task, how are configurations made? Is that command line activity? a config file? Would love to have it be easy to turn my @npub126nt...e9ll into my own content archive/backup, and even my own hosted solo relay if I felt inclined. Didn’t dive into the command line enough to learn if this is possible or maybe it’s not a good approach? But why? Do relays still gossip to other relays to have my content found by searchers, or is that not a thing and it’s just outbox model now? There are some questions I’ve had and, in some cases, still have. Maybe it stirs some ideas for you.