jb55 on Nostr: vitor suggested I rename this to something else since its not really communities. ...

vitor suggested I rename this to something else since its not really communities. it's much more like a threaded, distributed discussion protocol that is namespaced. not too different from the twitter model, but discussions can be grouped into specific topics. kind of like usenet/mailing lists... a bit like reddit... a bit like message boards. not sure yet. hey maybe it will be something new altogether. I will hack something together and see if its a gem or a turd.

quoting note166w…wxus

My nostr community idea:

- can only post in one community at a time.
- separate follow list for communities you’ve joined (relationship statuses ideally)
- communities have a name, banner, and description and can only be created once (name is immutable, non addressable). communities therefore have a specific sha2 ID which is the unchanging identifier for the community.
- non-addressable sha2 id over d-tag name anchor, otherwise it's not clear which "bitcoin" community you are referring to.
- 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 of the post in your timeline like in X)
- community can have addressable data associated with it via the creator or frost creators (sidebar info like on reddit)
- Since threads could be quite large, we should use [NIP-22 Comments](https://github.com/nostr-protocol/nips/blob/master/22.md), this would allow us to pull large root threads first (if building a reddit-style design)
- outbox: community author can create a preferred relay list for the community, or it can be more amorphous and exist everywhere
- cross sections of the community can be moderated if viewed from the perspective of moderated relays that host content from that community
- the community name changing would be confusing, immutable is good for the community creation anchor.
- description could be overridden with the addressable metadata event, but name can’t change
- 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.
- they have much better network effects as well and can exist for long periods of time as they can exist on any or all relays
- community members can publish relay lists and they can fight over which views of the network are the "official" ones, effectively forking the community without needing to change the root identifier
- the largest community for a given name would be the defacto “reddit community” for that identifier

Feel free to add questions and I'll add them to my notes here:

https://github.com/damus-io/notedeck/issues/788
note1euh…r3ra