nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z So here's an idea:
Instead of tagging a post with an 'a' tag to request that it goes into a community, the user publishes a new event that contains (stringified in the content field) the event he wants to post into the community, like how reposts work. This community post event would contain 'a' tags of all the communities the user wants to post into, as well as the 'e' and 'k' tags for the stringified event (just like kind 4550). For the sake of discussion, we can call this a "kind 4549 post request"
When mods create a 4550 post approval event, they can just copy the content string of 4549 post request event. All the tags are the same, so the person who created the request can still get notified that the post was approved.
If a user only wants his post to show up in communities, he creates whatever kind of event but does not publish that event directly — rather it gets posted as the content of a new 4549 event
If the user wants the post to show up in the main feed as well, he can publish the original event as well.
I like this solution it means event existing event kind can be posted into a community, not just text notes. (like long form, media, ect.) Communities would just have a modqueue of 4549 events.
The kind 1 post as the first post, as nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z pointed out exactly, it appears everywhere so people I follow I can see everything they post.
This is a design feature, not a bug. Of cause like all things, there’s always different school of thoughts, you can’t make everyone happy.
For this “4549” event it can be the exact same thing just like the existing kind 1 with “a” tag, but it’s a community only post. This could work.
I think doing a kind 1 copy is the easiest thing. We did the same for live activities.
But don't you think it would be boring if communities were only compatible with basic text notes?
Oh.. I didn't mean to be only compatible with the new event kind. It's still compatible with everything. But if people want, then there is a kind that would appear only inside the community.
Ah I see. But other event kinds would still appear on main by default, like if there was a community for kind 1063 photos. I guess the question is how big of a deal this will become in the future as communities develop and specialize in non-text-note events, i.e. if having a general way of preventing an event from showing up on main is worth the additional complexity.
I really think there is no need to exclude the community post in the main feed. in some sense, community is just like hashtag, you will never feel strange that people post something with hashtag appear on the main feed. community is just another way to do content filtering and classification.
Yup. It’s a design feature.
This was actually my initial take as well. But thinking about it a bit more, I don’t think it’s just filtering/classification. We already have hashtags and lists for that. Communities have different norms, formats, inside jokes etc. which make people reluctant to post if they know it’s going to main
thx for discussion. I get your point. and here is how I think about this: if people are reluctant to post on main feed, they should post to private communities(if there need such one). use another kind and hiding them on main feed doesn't solve their problem since people always have ways to find out what you post on the communities. instead, keeping public community post on main feed is actually a good reminder to people that this thing is not privacy.
Currently there are long form tagged with “a” tags too.
Yes, support all currently and future nostr content types is necessary
I agree with both of you, there is a lot of value in posts being able to be seen outside of community's as well. That is a good thing.
The only thing that would be better is if the user could control that behavior and choose which posts to show on main and which ones to keep as a community-only post.
> For this “4549” event it can be the exact same thing just like the existing kind 1 with “a” tag, but it’s a community only post.
Yeah exactly. The only reason I suggest having it be a "post request" that wraps an event (just like "post approval") is so that all the existing event kinds (e.g. long form, media) and whatever will be invented in the future is compatible with communities. Cause it would be boring is communities could only work with basic text notes, right?
