As you know, I'm not the most savvy about all this but I kind of feel like there's some putting of the proverbial cart before the horse... build your cart, let the horse grow strong. There's lots to do & only so many to do it. I haven't seen a single project or attempt to solve a problem that doesn't have a legitimate usecase.
Discussion
Yeah, I'm just seeing these complex structures being built for the most complex (but popular case). I don't think I'm asking for anything vastly new than whatever exists, but find it rediculous that devs are stuck on corralling the most complex situation to something that i see as already baked in.
Relays and clients are seen as separate things and so anyone that wants to create their own community needs to first use a single relay, create a new account and then white list it at the relay level. I really think the process can be easier. Sure we as a group are working on it, but it shouldn't be just us.
nostr:nprofile1qqs2js6wu9j76qdjs6lvlsnhrmchqhf4xlg9rvu89zyf3nqq6hygt0spzemhxue69uhhyetvv9ujuvrcvd5xzapwvdhk6qgdwaehxw309aukzcn49ekk2qghwaehxw309aex2mrp0yh8x6tpd4ehgu3wvdhk6ya985f & nostr:nprofile1qqsza748zkamgmw4he4hm2xhwqpxd5gkwju38wqh3twmtshx8kv8xvgpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcpz9mhxue69uhkummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctcktxuf5 feel you both have a bit to add to the conversation would love both your thoughts
Nostr offers the ability to publish in multiple communities (think publication houses) at once.
That is the game changer for me and means you do not have the false choice anymore between blasting your content out to the universe or publishing in a surgical community where the admin can rug you.
With nip-29 you can publish in any niche community that:
1. Overlaps with your contents topic/goal
2. You're willing to pay the price for
3. You're following the guidelines/rules of
Creating a high signal online world with organic discovery (and reporting) built in:
nostr:naddr1qqfyyet9wdqhye2rv9cxjarpd35hxarnqgs2js6wu9j76qdjs6lvlsnhrmchqhf4xlg9rvu89zyf3nqq6hygt0srqsqqqa287ywmff
I see nip29 and if that's what it takes - i'm for it. however, looking at the levels of complexity (read heterogeneity in users/relays) i see a very simple solution requiring ittle modification because its already baked in:
and
I'm uncaffeinated right now, so apologies if these are stupid questions but
Why would one need a new keypair to start a community?
What is too complicated about that process?
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?
Referring to amethyst specifically in that first couple sentences, I should have specified that.