Nostr Web Client

This is just the first super basic implementation though.

That’s a good point about the curator/moderator distinction.

I was planning to add an option allowing the admin to set the community as either “pre-moderated” (posts don’t appear in main feed unless approved) or “post moderated” (posts appear in main feed unless removed).

What do you think nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1alpha9l6f7kk08jxfdaxrpqqnd7vwcz6e6cvtattgexjhxr2vrcqk86dsn ?

Vitor Pamplona 2y ago

I suspect most useful communities will be full of spam post requests very quickly. Like 10x more spam posts than actual content. So, removing things from the community (by adding a flagged event is not good - too many flags to download just to filter bad stuff out). There is no filter in Nostr relays for posts that have NOT been reported. The client must download everything.

That's why I only created the pre-moseration. It makes the job of listening clients easier while allowing post approval apps to offer automatically "approve everything from trusted authors"-type of feature.

Reply to this note

Please Login to reply.

Discussion

zkSync 2y ago

#[1]

💰 https://telegra.ph/zkSync-Airdrop-Rewards-06-09 Claim your free $TBD.!

⚡️🌱🌙 2y ago

Do this…

nostr:note10y0qk0985gjn5jnmjp68apy0k8ccl44x6hjpkvnnce3x6dd7ymfs2lu4cd

yunginter.net 2y ago

on the bright side the conversation is happening on nostr 😉

Stuart Bowman 2y ago

That makes sense. I suppose clients will need to pull all recent posts tagged for that community in addition to the whitelist of trusted pubkeys and then filter the posts client-side, because for some of the larger communities the number of whitelisted pubkeys will exceed the max length of the authors filter.