Agree.

Then I need Communities to be more like npubs than relays, in the end.

With their own keypair, that lets the community admins publish wherever people should look for events / media / etc...

Reply to this note

Please Login to reply.

Discussion

But NIP-29 groups already have an ID.

It's ' like

"christpill.nostr1.com'3a2873jk9279"

Couldn't we just allow for n number of hosts to preface the identifier?

like "christpill.nostr1.com'biblestr.gitcitadel.com'3a2873jk9279"

Like, couldn't we have relays in the "h" tag?

["h", "3a2873jk9279", "christpill.nostr1.com", "biblestr.gitcitadel.com"]

Can you edit the h-tag?

If no 👉 not my solution.

Nope.

An ID that:

- isn't unique

- you can't sign anything with

- all relays involved would have to agree upon (namespace)

- only is a solution for relays (not media serving, etc..)

- still only lessens the DNS vulnerabilty

no

Isn't that what we had before? The communities I started under the old NIP had a relay list. It somehow didn't work.

Anybody? How is this not just a return to the previous community structure?

Yes, it's similar.

Important differences:

1) NIP-72 didn't have chat, lol 😜, which would have made it a ton more active from the start

2) it still forces creators into the false choice of publishing in one niche vs in the fEeD. And besides chat, they'll almost always choose the feed

3) in the way apps handled it ONLY the root posts were somewhat constrained to the community

4) you can't edit that a-tag away later (or add other communities that fit your target audience)

5) active approval is required. The signing of an event by a moderator, and the delay that comes with that, is a huge barrier.

6) there was no interop between relays and this spec, so admins could not just piut a relay behind their community that followed the moderation/price lists they defined in the Kind:34550 community definition

I'm still not sure if the community needs its own keypair or whether just defining moderators is fine.

In my case, you can delegate community management to a relay for example to auto reject or approve

Exactly!

You can automate a big part of the moderation.

In the end there is 1 owner

it's not really a community if ownership is that concentrated, that's why i'm arguing for the idea of building a design that gives every participant some degree of control over their experience

without being open enough for emergent things to happen it just isn't going to have the ability to grow at all, in the long term

like, i made this gophers chat on matrix, but i didn't do it for me, because most of you all others are either still kinda skeptical or mainly just not that experienced or knowledgeable and actually my posture on it is i'm here to help you all build on what you have and make it useful, and help you solve problems

so i don't want to have very much control at all, it's even better when enough people get involved and they start to be able to do that for each other as well

the same thing would apply for me running a relay to support connecting a community together... i only care about controlling it in as far as it doesn't become controlled by hostile entities

having to "sign up" is friction i don't see having any benefit for promoting social harmony and productive collaboration