There’s an simple, cross-relay, non-moderated community implementation that seems obvious to me but has not been spec’d yet… hrmm
Discussion
The whole point is moderation.
nah
I’m thinking large communities (100k+ people)
Ah ok. Like current Nostr? :haha:
Like this
I see. That's almost like a hashtag + a non-relay based algo.
With a #communikey you can do that. If you're very lax in your moderation (only focusing on proper topic + nsfw etc...) and you let the community keypair bring in appropriate content.
there are a bunch of important differences:
- can only post in one community at a time.
- separate follow list for communities you’ve joined
- communities have a name, banner, and description and can only be created once (name is immutable, non addressable)
- size of community is counted by number of people who have that community id on their community follow list.
- community posts have a distinct design (shows the community name on top like in X)
- community can have addressable data associated with it via the creator or frost creators (sidebar info like on reddit)
1) this can be a requirement of this #communikey → you can only post here and not target anywhere else
2) Yup, I will not even make those "Follows" a list, but labels instead (so apps can't mess up the list with each edit, etc...)
3) Interesting, can't give you that (yet)
4) Yup, can do that
5) All my UI widgets display the targeted Community(ies)
6) Yup
That immutable + non-addressable need is something i'll have to sleep on
I think the community name changing would be confusing, i think immutable is good for the community creation anchor. Description could be overridden with the addressable event, but name can’t change
Then basically the largest community for a given name would be the defacto “reddit community” for that identifier
Makes me think of maybe tying it to the wiki name for it. Dunno.
Yeah, that's a very good point.
If you think of something, let me know. I'll be ruminating too :thinking:
What if…
Implicit communities
Did i mis where you actually describe this obvious simple implementation?
writing my ideas here:
nostr:note1fuyhcze0pqgxkj6wy84h9scexretmthhurrufpmn05jnyadzp3tqm87kca
if the name is the d-tag is immutable...
i wanted it to have a persistent sha2 id though, otherwise it's not clear which "bitcoin" community you are referring to
it would be like a channel and with nip-72 group it would be a "discord" like, a site like https://asknostr.site/ browse tags like "reddit", it has no community, but you said "simple"
nostr:npub18jp8mdkytalxyg06zxdevpzwkxjpy9r2rat8gapgwnmmyejp3lps7edjnx what are thoughts on a non-moderated community?
What does that mean? Non moderated
there is a moderated communities spec, it's an alternative to that
cross sections of the community can be moderated if viewed from the perspective of moderated relays that host content from that community
Sorry but I am not a dev and I need simple language from the POV of the users.
What is a community in NOSTR? Where do you create it? And if I got it right if the community is putting content that does not want any moderation this spec will allow it to be uncensorable even by relays. Do I get it?
There is no singular definition of a community on nostr. I am proposing one of many alternatives.
in this model noone can stop you from posting to a community. the community would exist as notes spread across different relays.
there could be a canonical relay list associated with the community, but there could be forked or hidden parts of the community on unofficial relays. these are just different views of the community associated with the sha2 id of the community.
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s Nackoo’s frame of reference is a admin/moderated telegram community with channels.
Non-moderated generally means no admin.
However, if you are running a relay on which the community operates there is an admin capability (i.e. can whitelist, blacklist etc).
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s does your spec envision a community that can be run solely on one relay, or multiple relays?
this is all covered in https://github.com/damus-io/notedeck/issues/788 so far
specifically:
- cross sections of the community can be moderated if viewed from the perspective of moderated relays that host content from that community
- in this model noone can stop you from posting to a community. the community would exist as notes spread across different relays. there could be a canonical relay list associated with the community, but there could be forked or hidden parts of the community on unofficial relays. these are just different views of the community associated with the sha2 id of the community.
I would like to see the NIP proposal.
gonna build something first before I NIP it
Cool! I'm looking forward to it.
Starting to write some ideas here: