There’s an simple, cross-relay, non-moderated community implementation that seems obvious to me but has not been spec’d yet… hrmm
Login to reply
Replies (35)
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
Yeah, that's a very good point.
If you think of something, let me know. I'll be ruminating too :thinking:
Makes me think of maybe tying it to the wiki name for it. Dunno.
@Nackoo2000 what are thoughts on a non-moderated community?
I would like to see the NIP proposal.
gonna build something first before I NIP it
What if…
Implicit communities
NIP it in the bud
Cool! I'm looking forward to it.
Did i mis where you actually describe this obvious simple implementation?
writing my ideas here:
View quoted note →
What does that mean? Non moderated
there is a moderated communities spec, it's an alternative to that
Mauve has more RAM?
if the name is the d-tag is immutable...
cross sections of the community can be moderated if viewed from the perspective of moderated relays that host content from that community
i wanted it to have a persistent sha2 id though, otherwise it's not clear which "bitcoin" community you are referring to
Divide and conquer? Communities and be divided into a "compliant" and "non-compliant" part depending on which server posts are hosted.
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.
@jb55 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).
@jb55 does your spec envision a community that can be run solely on one relay, or multiple relays?
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 like the idea of forking, it's what makes Open Source software great. At least the *threat* of it does. In the end when you fork a codebase you fork the community so we have plenty of precedent for that.
But I don't know if a community is a community if there are "forked or hidden parts". The forked community is a different community, sha2 token be damned.
You can't have shape shifting communities like that. It needs to be clearly defined. Just look at European countries right now that are experimenting with shifting definitions of who's in who's out. It's not working.
it would be like a channel and with nip-72 group it would be a "discord" like, a site like 
browse tags like "reddit", it has no community, but you said "simple"
Asknostr.site
#asknostr - Q&A site powered by Nostr
This website is a Q&A community on top of Nostr. The purpose of the site is showcase the power of a decentralized social network protocol and allow...