Vivek on Nostr: I like this proposal. This - allows any event kind to play with communities - allows ...
I like this proposal. This
- allows any event kind to play with communities
- allows unmoderated feed to be displayed
- allows notifications of approvals
- allows a mod queue display
I have a few questions though:
- 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
- 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?
- in case the user doesn't want the new note in their feed, there will be no "e" tag in their post request, right? I think it is a neat way to ask A client not to look for the actual event.
- allows any event kind to play with communities
- allows unmoderated feed to be displayed
- allows notifications of approvals
- allows a mod queue display
I have a few questions though:
- 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
- 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?
- in case the user doesn't want the new note in their feed, there will be no "e" tag in their post request, right? I think it is a neat way to ask A client not to look for the actual event.