-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
implement pending approvals #18
Comments
Do we need to change the code in challenges to implement this? Is pending approvals only for posts? Or does it include replies and votes? |
yes, e.g.
I guess you would need to write the logic for checking if a
The pendingApproval option applies to all comments, replies and posts. But not to votes. It's possible to combine pendingApproval with exclude to only target replies or posts. I could potentially modify getChallengeVerification() myself since I'm most familiar with the code, but I don't know when I'm gonna have time to do that, if you can do it that would be good. NOTE: I don't think pendingApproval needs to be added to challengeVerificationMessage, just to ChallengeVerificationMessage.publication.pendingApproval might be fine. |
Shouldn't |
seems desirable to me. we want plebbit to be as transparent as possible
a lot more complex to implement, also pubsub requires as lot more resources than just fetching ipfs/ipns, which can also just be done from a gateway. we want to avoid pubsub as much as possible, it's the least scalable part of plebbit. also I dont think them not being publicly visible is desirable, we want plebbit to be as transparent as possible. |
The challenges API for pending approvals should be:
other APIs related to pending approvals:
the pending approval comments would be visible on
subplebbit.posts.pageCids.pendingApproval
, the list would cut out atsubplebbit.settings.maxPendingApprovalCount = 500
, comments pending approval would containcomment.pendingApprovalId: 'random string'
the approvals would be sent by doing
createCommentEdit({pendingApprovalId: 'random string', approved: true})
ChallengeVerificationMessage.publication.cid
should be defined (so the author can start listening for a comment update), but the sub owner should not pin this CID yet or start publishing comment updates (to save resources for not yet approved and never approved comments)ChallengeVerificationMessage.publication.pendingApproval = true
should be defined, but should not be part of thecommentIpfs
since it doesn't seem to serve any purpose, the goal is just to signal to the author that his comment is pending approval, once the CID is fetchable, thependingApproval
value will always be false, so no reason to include it incommentIpfs
The text was updated successfully, but these errors were encountered: