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.
How to edit a post for small modifications without affecting the visibility of other posts?
Related: Could we have a way to edit without bumping posts?
Motivation
I usually edit my own posts a lot of times in order to improve them. This put the corresponding post on top of the "main post page list" (for e.g. meta.codidact.com).
However, most of the time I do very little changes to my post (correct a typo, add a link, etc.), so it does not deserve to draw attention to the post in question.
So my post takes the place of other posts that would need more attention...
In this case, a general recommendation could be: "Avoid editing a post for small modifications (e.g. correct a typo) because it affects the visibility of other posts"
Starting from this postulate (which could obviously be discussed ;-), the question is:
How to edit a post for small modifications without affecting the visibility of other posts?
Proposal
A solution could be to allow the author of the edit to choose if they wants to put the post on the top of the list or not (the default behavior could be to move the post on top, as it is currently done).
This could be achieved, for e.g., by adding a check box at the end of the edit view which could look like this:
I like the idea, and I was going to suggest it myself. However, I also understand the concerns of @trichoplax about t …
1y ago
I like this, but... I've often wanted this feature. I feel bad about cluttering the top of the question list when I mak …
1y ago
Maybe when our communities are much larger I share the others' concerns about getting fresh eyes on edits to avoid ab …
1y ago
3 answers
You are accessing this answer with a direct link, so it's being shown above all other answers regardless of its score. You can return to the normal view.
Maybe when our communities are much larger
I share the others' concerns about getting fresh eyes on edits to avoid abuse (or even just errors that would motivate a re-edit). As things stand, I think the concern about "drawing away attention" is greatly overstated. I'm generally willing to look at an entire page or so of results to try to find something I can actually answer, and I doubt I'm in the minority there. And, well, right now most of our communities have content dating back a year or more on the front page. On many sites, the most recent unanswered question dates back a year or more, too. So bumping your already relatively recent stuff is just not causing that much of a distraction. Bumping an answered, 2-year-old question could cause a problem if it weren't a rare occurrence, but there's still the option to search/filter for unanswered questions (we should probably make this easier!)
However, in a world where Codidact gets much larger and communities are receiving several posts per hour, I can see where there could get to be real competition between new questions and edits. It would become useful to have the default front-page view sort by the OP post date, but have a separate, easily-selected view that sorts by the most recent modification. It would also be useful for the "Edits" tab for categories to show recent unilateral edits, as well as just pending edits.
0 comment threads
I like this, but...
I've often wanted this feature. I feel bad about cluttering the top of the question list when I make a minor typo fix on an old post.
However, having thought about it more over time, I can see a problem with letting a user decide which of their edits should be visible.
Misuse
If a user wants to make an edit that they expect will be disapproved of, and that may lead to their post being flagged for moderator attention, being able to keep their edit from appearing at the top of the question list would allow them to make the edit with much reduced risk of detection.
Moderation
One solution to this would be to allow the edit to be kept off the top of the question list, but notify moderators that the edit has been made so they can check this unscrupulous usage is not happening. However, this diverts work that can be done by the community to being only done by the moderators.
I see a moderator's role as dealing with overflow. A moderator should be solving problems that the community cannot solve. Anything that the community can deal with itself should not be referred to moderators. This leaves the maximum amount of moderator time available for the things that only they can handle.
Community moderation
For this reason I think it is important that every edit, no matter how small, results in the post going to the top of the question list. This way the editing user does not get to decide whether their edit is seen by the community, and the community can spot problems (and flag if necessary) rather than putting the full burden of monitoring all edits on a small number of moderators.
2 comment threads
I like the idea, and I was going to suggest it myself.
However, I also understand the concerns of @trichoplax about the risk of abuse, e.g. "sneaky edits" that could fly under the radar.
I think a nice tradeoff solution would be IMO:
-
Allow minor edit checkbox only for people that have the edit privilege, just to filter out users that haven't shown some pattern of responsible editing behavior. In other words, suggested edits will always be bumped (maybe let the people authorizing the edit to choose whether the edit warrants a bump?).
-
For people doing an edit on their own posts and without the edit privilege, enable the checkbox, but change the behavior: the checkbox doesn't suppress bumping, it delays it until some time has passed from the latest edit (say 1h), so that people that make a flurry of small edits to their own posts can do that without multiple bumps. All the edits are "bumped together" once that time has elapsed from the last edit in the series. Moreover, to avoid people gaming the system by continuously editing the post to postpone a bump forever, bump the post anyway after some other given time (say a day).
-
Provide a new visualization option for posts, e.g.
show minor edits, so that people wanting to check what's happening "down in the noise" can do that. In other words, the "minor edit" checkbox doesn't prevent the edit to be discovered by people wanting to check that out. In this way mods could periodically check the posts with minor edits just to see if something shady is going on. -
To avoid careless bumping by privileged users, check the checkbox by default if the user hasn't changed much of the post, and also remind them they are going to perform a "minor edit" with some visual cue. In this way, a major edit is bumped unless the user wants otherwise, whereas a minor edit is not bumped, unless the user wants otherwise.
Note that in my idea the final choice is always on the (privileged) user (no forced choices). The system just lends a hand and suggests the most logical/common behavior (focus on personal responsibility here).
1 comment thread