Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Post History
Suppose we have a post author A and a comment author B. Here's a simple proposal for addressing the problem. When B writes the comment, the UI offers B a checkbox to "allow A to propose resolu...
Answer
#2: Post edited
- Suppose we have a post author A and a comment author B. Here's a simple proposal for addressing the problem.
* When B writes the comment, there is a checkbox that allows A to "propose resolution" to the issue with a reply comment.* When A comments, similarly, there would then be an option to mark the comment as a resolution for B's comment. B is notified by the system (as would happen anyway, as things currently stand) of A's comment, and can thus see A's assessment of the situation along with any edit that was made to the post.- * When this process has been followed all the way, then B would be given an option in the interface to delete both comments, simultaneously. (This might generate a system message back to A, without any corresponding new comment.)
Cooperatively extending permission like this ensures that both parties are on the same page, and can't trample on each others' rights and freedoms as a Codidact user. This would be especially useful for comments made to indicate a problem with a question - perhaps ones that are prompted by an [enhanced flag-for-closure interface](https://meta.codidact.com/posts/289687).
- Suppose we have a post author A and a comment author B. Here's a simple proposal for addressing the problem.
- * When B writes the comment, the UI offers B a checkbox to "allow A to propose resolution" to the issue.
- * If that option was chosen, when the system notifies A about the comment, it indicates the possibility of proposing a resolution by replying after making any necessary fixes. (This might include not fixing anything and replying e.g. "no, that's exactly what I intended it to say".)
- * When A makes the reply comment, there would then be an option to mark the comment as a resolution of the issue B raised. As usual, B is notified by the system of A's comment, and can thus see A's assessment of the situation along with any edit that was made to the post.
- * When this process has been followed all the way, then B would be given an option in the interface to delete both comments, simultaneously. (This might generate a system message back to A, without any corresponding new comment.)
- Cooperatively extending permission like this ensures that both parties are on the same page, and can't trample on each others' rights and freedoms as a Codidact user - all without needing to get anyone else involved. This would be especially useful for comments made to indicate a problem with a question - perhaps ones that are prompted by an [enhanced flag-for-closure interface](https://meta.codidact.com/posts/289687).
#1: Initial revision
Suppose we have a post author A and a comment author B. Here's a simple proposal for addressing the problem. * When B writes the comment, there is a checkbox that allows A to "propose resolution" to the issue with a reply comment. * When A comments, similarly, there would then be an option to mark the comment as a resolution for B's comment. B is notified by the system (as would happen anyway, as things currently stand) of A's comment, and can thus see A's assessment of the situation along with any edit that was made to the post. * When this process has been followed all the way, then B would be given an option in the interface to delete both comments, simultaneously. (This might generate a system message back to A, without any corresponding new comment.) Cooperatively extending permission like this ensures that both parties are on the same page, and can't trample on each others' rights and freedoms as a Codidact user. This would be especially useful for comments made to indicate a problem with a question - perhaps ones that are prompted by an [enhanced flag-for-closure interface](https://meta.codidact.com/posts/289687).