Oddbean

It's more about the situation where you want to have your own echo chamber and move across clients. You're not doing that with your normal account right now becaus you have your relay set which will follow you around any client. Basically wide open all the time. If you want your echo chamber you'd need a new account to log in to so that way you get a smaller feed because that account is only connnected to one relay. Sure, /theoretically/ you can do that with a normal account to post your kind1 notes but you'd have to manually set your relays each time you want to change the scope which is a user nightmare. Computationally this should be a simple task though, which I relate as very similar to how Amethyst's can change feeds with lists or hashtags. If that is the most basic functionality that is already covers massive ground.

Its a few steps but I think user nightmare is a bit strong of terminology for it.😅 It could be simplified for reading, but writing is super easy. And where does hopping clients come into this? Each should have various purposes... is there anything that prevents a client from being developed that respects your relay list but only actually reads from specified choices? Or accepts only certain event types, sort of like Fountain is working towards? Do you think a lack of support comes from that this concept isn't conducive to strengthening censorship-resistence more broadly, given the current state of relays & connection? Because, really I should be able to write this reply to my own relay & no other, but if I did you likely wouldn't see it, as things stand. (I mean, you *might* but really you should no matter what) Again... I'm just thinking it's too early yet. But maybe I'm missing something?