StackExchange sites have a "Community" user bot that occasionally bumps questions under certain circumstances:
- The question is open and not deleted
- The question was not recently active
- The question's score is not negative
- The question has no positively-scored answers (more upvotes than downvotes)
- The question has at least one non-deleted answer with zero score (no votes, or up & down votes cancel out)
- The question is at least 30 days old
- It's been at least 120 days since the bot bumped this question
It ranks the top 100 questions that meet these criteria by view count, and randomly selects one to bump to the top of the Active Questions feed, about once per hour.
The intention is to help good questions that maybe didn't get the attention they needed when first posted occasionally see sunlight, so a passing user might give them an answer, or confirm an existing answer is good by upvoting it. It also helps keep the active questions feed from stagnating when new activity is low.
Unfortunately, during periods of very low traffic, this automated bumping completely outpaces non-bot user activity, and we end up with a top page that looks like this:
That's 12 community bumps in a row. In total today 79% of questions on the main feed today are Community bumps.
This has the effect of burying new content and folks looking for answers today - usually behind questions that show a long history of drawing no engagement (so they may be unanswerable, abandoned, etc.).
We can combat this to some degree by clicking on these Community Bump questions and...
- Upvoting a zero-score answer, if it's decent (or editing it until it's upvote-worthy)
- Downvoting all zero-score answers, if they're all bad
- Adding a new answer of higher quality to attract new upvotes
- Voting to close the question if it's off-topic or can't be answered well in its current form
- Down-voting the question to a negative score
- Flagging zero-score "answers" that are not answers, to be deleted or converted to comments by the mods
Any of these actions can prevent the question from being bumped again, and I encourage doing this whenever you can. But since we have such a huge backlog of bumpable questions, this alone won't solve it.
StackExchange has a feature to mitigate this, which skips Community bumps if any of the top
n questions on the Active Questions feed were themselves bumped there by the Community bot.
Currently the Expression Engine, Hardware Recommendations, and Japanese StackOverflow sites use
n = 5 to stop bumps if any of the top 5 most-recently-active questions are Community bumps.
Should we request enabling this limit here too? And if so, what threshold
n should we use?