Nostr Web Client

So this is an important question — right now everything posted in a NIP-172 community will show up in your profile feed too. I think there are pros and cons to this.

Pros of showing community posts in profile feed:

1) Promotes discoverability of communities, i.e. there can be a link next to posts like "posted in n/such-and-such"

2) Helps "bootstrap" communities since other users don't have to specifically go to that community or even know that it exists to engage with content posted there.

Cons of showing community posts in profile feed:

1) A user's profile feed may get filled up with notes from communities that are not particularly relevant to a wider audience

2) There may be certain posts that a user doesn't *want* to be easily discoverable by a wider audience

This is the problem inherent in trying to combine the *breadth* of Twitter-like content with the *depth* of Reddit-like content.

So what to do about it?

One idea I had for a solution would be to allow users to mark communities as "visible" by adding an `a` tag to their kind 0 metadata event. That way Twitter-like clients could know to only display posts from these communities in the user's main feed.

Thoughts? nostr:note17gv07xnqyf90h7tth4zzmgwx7q2v8wva5j8ygsz2jf34lgfrx8xs8hzkh3

Vitor Pamplona 2y ago

We should probably hava a kind 1 just for communities. If people post in the community page, it goes with that kind. They can also do kind 1 and it will show in both places.

Reply to this note

Please Login to reply.

Discussion

Stuart Bowman 2y ago

You mean have a new kind for community posts? That could work, but the drawback I see is that it limits communities from being able to take advantage of all the kinds of notes that already exist. For example, with Satellite I was planning to add the ability to display long-form posts, as well as media (kind 1063) posts. That was why I thought your original idea to just mark any note as a "post request" with an `a` tag was such a good idea.

Vitor Pamplona 2y ago

Yes a new kind, but just for kind 1. Then make it a choice to use kind 1 or the new kind. Every other event type can be reused.

Stuart Bowman 2y ago

I see. Not a perfect solution, but I suppose for the other event kinds, the Twitter-like clients could just hide all events with an a tag. I still think allowing users to whitelist communities that should be aggregated is a good idea. Implementing that wouldn’t conflict with anything, it would just be a client-side thing