Create 05.md 0 simple community DIP

[alltheseas]

simply community DIP

[danieldaquino]

I couldn't update the PR (I do not have the permissions), but I tweaked the draft:
05.md

cc @jb55 @alltheseas

[alltheseas]

Looks good @danieldaquino. I updated the draft PR to reflect your revisions, additions, and elaborations.

@jb55 let us know if you have comments, and if it's ready for sharing with other nostr devs.

[alltheseas]

@danieldaquino based off feedback, and current 'communities' platform usage patterns, a subtle job-to-be-done might be fine-grained "channels" of a community. In e.g. Discord, or Telegram there can be groups/communities with multiple channels (e.g. general channel, developer channel, meetup/event channel, marketing channel etc.).

As proposed, does this DIP allow for creation of channels, within a community?

[jb55]

I couldn't update the PR (I do not have the permissions), but I tweaked the draft: 05.md

cc @jb55 @alltheseas

don't have the permissions to PR? since when do you need permissions to PR something on GitHub? I'm confused

[jb55]

how do I pull down topic thread roots without the replies?

[danieldaquino]

@danieldaquino based off feedback, and current 'communities' platform usage patterns, a subtle job-to-be-done might be fine-grained "channels" of a community. In e.g. Discord, or Telegram there can be groups/communities with multiple channels (e.g. general channel, developer channel, meetup/event channel, marketing channel etc.).

As proposed, does this DIP allow for creation of channels, within a community?

Currently no, this was designed to be more like a "reddit-style" community than a "discord-style" one.

[danieldaquino]

how do I pull down topic thread roots without the replies?

@jb55, you would query for an I tag. In the current draft version, this type of query will not return thread replies, because those replies would be constructed using E and e tags and would have no I tags.

Relevant section from the draft:

Each post can have its own thread. Threads are simply NIP-22 comments with root E and e tags (pointing to the root thread post, and the parent response — respectively).

[jb55]

Oh right!