Take a look at https://satellite.earth for Reddit-like UX

Satellite uses NIP-42 for auth. Docs here: https://github.com/lovvtide/satellite-web/blob/master/docs/cdn.md

nostr:npub1lr2zzf989mvf393y0tv39ara6a4vddkd6y87z784up9vl6ks6j3qtudl6a Satellite allows you to upload videos up to 5GB with unlimited bandwidth, I think nostr.build is similar

Interesting, I like this idea! Like "sort by active"... I will think about how to implement this, thank you

nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub16zsllwrkrwt5emz2805vhjewj6nsjrw0ge0latyrn2jv5gxf5k0q5l92l7 here you go

https://satellite.earth/cdn#upload

Sure you could always repost any note, but it would be simpler to just publish the original kind 1 directly. The whole point of the post request event is to itself act as a kind of repost *into* a community.

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

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.

But don't you think it would be boring if communities were only compatible with basic text notes?

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?

> After a person clicks the submit button after composing a community note, he will see two popups from the signer extension . Not sure if that would startle them as generally only one is expected

Good point. Although when posting an existing note into a community, the user will only be signing one event. (that's actually one additional benefit of this approach, it allows users to "pull" other notes into communities with kind 4549 events, just like how mods can pull events into communities with kind 4550 events)

> When someone zaps or reacts to a community post, we need to make sure to count it against the post request and not the approval event or the orginal kind 1 event if it exists. Is my understanding correct?

Correct, that's my understanding as well. Zaps/reactions would go to the post request, since that event will be present and indexed on relays.

> in case the user doesn't want the new note in their feed, there will be no "e" tag in their post request, right?

Actually I think it *would* make sense to include the 'e' tag so that clients can query to find all the post requests for an event (this would be relevant when an existing note was posted-requested into a community).

> I think it is a neat way to ask A client not to look for the actual event.

Well clients that don't support communities are not going to pull the kind 4549 post-requests in the first place, right? So they'll never have any reason to look for the actual events. And clients that *do* support communities won't need to look for the events since they already have the actual events (they can parse them from the content string)

Thanks for the in-depth response, and please let me know if I misunderstood any of your points!

Satellite update: deployed "conversations" tab

Now you easily can keep track of (and get notifications for) all the threads you've recently been involved with. You can even reply directly in from the notifications UI without having to navigate to the thread.

Check it out.

Interesting — I'm not suggesting to encrypt the event though.

What do you think about this being a way to control community posts showing up in the main feed?

Cause (I agree with you) that we need new event kind for community posts, I'm just saying why not use the new event kind to wrap up the event you're trying to post into the community.

That way communities are compatible with all event kinds. Just wrap em up

nostr:npub1ltx67888tz7lqnxlrg06x234vjnq349tcfyp52r0lstclp548mcqnuz40t nostr:npub1alpha9l6f7kk08jxfdaxrpqqnd7vwcz6e6cvtattgexjhxr2vrcqk86dsn nostr:npub10awzknjg5r5lajnr53438ndcyjylgqsrnrtq5grs495v42qc6awsj45ys7 thoughts on this idea? We need a way for users to control whether community posts show up in the main feed nostr:note13hr0j93760sueknc3rgvpu6f0qy6yyusasvfrdssp7c3jmnmg8wssww62n

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.

Hey nostr:npub15879mltlln6k8jy32k6xvagmtqx3zhsndchcey8gjyectwldk88sq5kv0n I'm the developer of Satellite. The issue you're describing is not something I can change on without changing the way that communities work on a protocol level (NIP-172 specifically). I actually agree with you there there should be a way to control which posts show up on your main timeline, and I was talking with nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z about this a few days ago. These communities are very new. I'm sure we'll get the UX hammered out soon.

Community chat—interesting! Looking forward to checking it out.

Hey I'm the developer.

If you want bigger text try pressing the Command/Ctrl and Plus keys to increase your browser zoom, it works quite well.

Glad you're enjoying Satellite—lot's more updates coming soon!

One fundamental difference, perhaps the most important, is that mod actions are transparent

That's what I'm working on now!