Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

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

60%
+1 −0
Q&A Notifying each other that a commented-on issue is resolved, to produce fewer comments rather than more

The exchange that provoked this question, happened on one of my answers. I wrote the response to you, to acknowledge your helpful comment, and to notify you that you were indeed right. In addition...

posted 1y ago by Andreas witnessed the end of the world today‭  ·  edited 1y ago by Andreas witnessed the end of the world today‭

Answer
#2: Post edited by user avatar Andreas witnessed the end of the world today‭ · 2023-09-18T13:31:59Z (about 1 year ago)
  • The exchange that provoked this question, happened on one of my answers.
  • I wrote the response to you, to acknowledge your helpful comment, and to notify you that you were indeed right. In addition to pointing out the typo in my post, you also said you were unsure about what I really meant. As such, I wanted to give you a ping, so you'd be notified the issue was resolved. I then flagged your comment as "No longer needed", and expected you to do the same with mine once you had read it.
  • Had you only pointed out the typo, and not also written that you were unsure about the meaning of my text, I would have just marked your comment as NLN, and omitted replying.
  • Currently, Codidact only has custom flagging reasons for comments; there should also be "spam", "rude/abusive" and "no longer needed" in addition to the custom moderator flags. This better tells the user the expected uses of comment flags, and for the case of NLN, that flags are not necessarily a harsh way to deal with content. This is the same way it works on SE. There's also the possibility that Codidact should explore another way of handling this matter. The proposed solution of this answer is merely a slight improvement over the SE way. It's not necessarily the best way, and I'm open to other ways of doing it.
  • It should be preferred to avoid moderator intervention for this simple matter. In addition, the volatile "thanks + elaboration" is sent to the feedback giver for a reason; it's preferable that this isn't purged before the recipient gets the chance to read it. (A "thanks" without elaboration is pointless, and shouldn't be posted in the first place).
  • One way to solve this, is to notify users once their comments are marked NLN. For this specific case, it would be clear from the revision history of the answer what the "elaboration" of the comment would have to be. This still requires that the user then manually deletes their own comment. Experienced users should have no issue with this, but new ones are likely to find this confusing.
  • Another way is to let users mark their comments as automatically deletable by NLN flags from a specific flagger, that being, the one they pinged, either explicitly, or implicitly. This would let a feedback receiver remove the feedback once acted upon, although it also allows them to misuse this ability to remove said feedback without acting on it. That may sometimes be a mild abuse, though in most cases, likely just due to a misunderstanding.
  • The exchange that provoked this question, happened on one of my answers.
  • I wrote the response to you, to acknowledge your helpful comment, and to notify you that you were indeed right. In addition to pointing out the typo in my post, you also said you were unsure about what I really meant. As such, I wanted to give you a ping, so you'd be notified the issue was resolved. I then flagged your comment as "No longer needed", and expected you to do the same with mine once you had read it.
  • Had you only pointed out the typo, and not also written that you were unsure about the meaning of my text, I would have just marked your comment as NLN, and omitted replying. Although, the correct course of action if you are fully convinced it's a typo, and what the correct text is supposed to be, is to suggest an edit to the post.
  • Currently, Codidact only has custom flagging reasons for comments; there should also be "spam", "rude/abusive" and "no longer needed" in addition to the custom moderator flags. This better tells the user the expected uses of comment flags, and for the case of NLN, that flags are not necessarily a harsh way to deal with content. This is the same way it works on SE. There's also the possibility that Codidact should explore another way of handling this matter. The proposed solution of this answer is merely a slight improvement over the SE way. It's not necessarily the best way, and I'm open to other ways of doing it.
  • It should be preferred to avoid moderator intervention for this simple matter. In addition, the volatile "thanks + elaboration" is sent to the feedback giver for a reason; it's preferable that this isn't purged before the recipient gets the chance to read it. (A "thanks" without elaboration is pointless, and shouldn't be posted in the first place).
  • One way to solve this, is to notify users once their comments are marked NLN. For this specific case, it would be clear from the revision history of the answer what the "elaboration" of the comment would have to be. This still requires that the user then manually deletes their own comment. Experienced users should have no issue with this, but new ones are likely to find this confusing.
  • Another way is to let users mark their comments as automatically deletable by NLN flags from a specific flagger, that being, the one they pinged, either explicitly, or implicitly. This would let a feedback receiver remove the feedback once acted upon, although it also allows them to misuse this ability to remove said feedback without acting on it. That may sometimes be a mild abuse, though in most cases, likely just due to a misunderstanding.
#1: Initial revision by user avatar Andreas witnessed the end of the world today‭ · 2023-09-17T22:52:41Z (about 1 year ago)
The exchange that provoked this question, happened on one of my answers. 

I wrote the response to you, to acknowledge your helpful comment, and to notify you that you were indeed right. In addition to pointing out the typo in my post, you also said you were unsure about what I really meant. As such, I wanted to give you a ping, so you'd be notified the issue was resolved. I then flagged your comment as "No longer needed", and expected you to do the same with mine once you had read it. 

Had you only pointed out the typo, and not also written that you were unsure about the meaning of my text, I would have just marked your comment as NLN, and omitted replying.

Currently, Codidact only has custom flagging reasons for comments; there should also be "spam", "rude/abusive" and "no longer needed" in addition to the custom moderator flags. This better tells the user the expected uses of comment flags, and for the case of NLN, that flags are not necessarily a harsh way to deal with content. This is the same way it works on SE. There's also the possibility that Codidact should explore another way of handling this matter. The proposed solution of this answer is merely a slight improvement over the SE way. It's not necessarily the best way, and I'm open to other ways of doing it.

It should be preferred to avoid moderator intervention for this simple matter. In addition, the volatile "thanks + elaboration" is sent to the feedback giver for a reason; it's preferable that this isn't purged before the recipient gets the chance to read it. (A "thanks" without elaboration is pointless, and shouldn't be posted in the first place).

One way to solve this, is to notify users once their comments are marked NLN. For this specific case, it would be clear from the revision history of the answer what the "elaboration" of the comment would have to be. This still requires that the user then manually deletes their own comment. Experienced users should have no issue with this, but new ones are likely to find this confusing.

Another way is to let users mark their comments as automatically deletable by NLN flags from a specific flagger, that being, the one they pinged, either explicitly, or implicitly. This would let a feedback receiver remove the feedback once acted upon, although it also allows them to misuse this ability to remove said feedback without acting on it. That may sometimes be a mild abuse, though in most cases, likely just due to a misunderstanding.