在某些类别中，定期自动提升旧话题的活跃度是合理的。
在买卖类类别中，当话题处于开放状态且商品仍在出售时，定期提升其可见度是有意义的。
在 Support 类别中，如果旧话题被遗忘，提升其活跃度可能也是合理的。
迄今为止，提升可见度的唯一方法是“编辑”话题的最后一篇帖子，或发布一条 bump 回复。
这两种方案都不够理想。
我们刚刚添加了一个新的类别设置：每日自动提升的开放话题数量。默认情况下，该值设置为 0，不会进行自动提升。不过，您可以调高该数值（在 meta 类别中，我们在 Support 中将其设置为 3）。
它的作用是什么？
如果存在一个未关闭、未解决、可见、未归档、非类别描述且未置顶的话题，且该话题在过去 24 小时内未被提升过。
系统将查找 N 个最旧的已提升话题，并将其提升至首页。该过程每 15 分钟最多提升 1 个话题，并受到速率限制，因此每天仅执行 N 次提升（N 由您设定）。
such a nice and needed feature! thanks for developing this 
This seems very fast, especially if a forum doesn’t have such dynamics.
can this time be tuned based on the the number of N: e.g. time_interval = 24hours/N, so that there’s a uniform dynamic for old topics during the day?
Also if the topic is older than some months, there exists this system-notification which tells users that “the topic is old, and are you sure you want to answer it?!”
this makes users a little bit confused: from one hand admins bumped the topic to make it more visible and “get replies”, and from the other hand system is telling users “do not contribute”!
Really nice idea!
Will it be indicated somehow that it’s bumped?
I also think this would be good - it’s a bit confusing to see super old topics at the top of ‘latest’. How about adding a ‘small action’ whenever the topic is bumped. Something like:
If the most recent post in the topic is an auto-bump small action, edit it rather than creating a new one. That way we keep noise to a minimum.
Yesterday I lamented re-starting a thread that was over 6 months old (I think because it was in recommended topics), not realizing that it was over 6 months old. Several people participated in a thread that I thought was current, but it wasn’t. I was embarrassed that I’d cranked up the topic again.
Now when I go to latest, I’m recommended https://meta.discourse.org/t/custom-print-style-should-be-added/14921/12 , which is from April 14. (And it’s on almost the same topic that I replied to errantly yesterday) And when I look at it in Latest I see that there’s “activity” 14 minutes ago, except, there’s really not activity in over 3 years.
It was confusing enough when Suggested would send me to long-dead topics that don’t need to be revisited, but now I can’t tell from Latest whether I should visit a topic.
I’m having a hard time understanding the value of this feature.
I like the idea of the auto bumped small action, not sure how @codinghorror feels about
@Pad_Pors I have a nice idea of how to space out the bumps, will implement tomorrow
Having these forever open support topic is a problem, I like that this triggers us to clean up, an alternative I guess is just to auto close all old support topics, but it is a bit more drastic
That makes sense. It seems that topics are more likely to be closed lately, so perhaps this will be less annoying once that clean-up is done. It seems rather painful (for me, anyway) until that’s done, though.
Perhaps it would be safe to auto-close stuff that’s, say, a year or two old?
First of all there is a cap of one year on suggested so your statement isn’t correct.
Second, it is completely valid to continue the same discussion later if it was not resolved. Of course you did not know it was resolved, which is understandable since you can only trigger “real” printing mode from a keyboard shortcut… which is quite undiscoverable…
Proceed on auto-bumped small action @sam, this makes sense, because “invisible magic” always leads to confusion.
Really nice feature 
One suggestion: Add integration with discourse-solved plugin and add the ability to choose non-closed and/or non-solved posts
This resolves the 2 big issues with the initial system:
We spread out bumping through a 24 hour period. If you are autobumping 4 topics in a category, then it is one per 6 hours.
We add an auto bump message at the bottom of the topic so you can tell why it floated to the top
@barreeeiroo I love the idea of integrating with solved … we need to create a hook for it in core though, will work on this now!
A post was split to a new topic: Improve usability of reply as new topic
Per:
And:
This now integrates with Discourse solved and will not bump solved topics.
@eviltrout / @tgxworld not sure if you ever needed to do this before, but this seems like the best pattern for composable filters I can come up with without adding a proper filter interface (or leaning on the only used in one plugin, filter interface I added years back)
on(:filter_auto_bump_topics) do |_category, filters|
filters.push(->(r) { r.where(<<~SQL)
NOT EXISTS(
SELECT 1 FROM topic_custom_fields
WHERE topic_id = topics.id
AND name = 'accepted_answer_post_id'
)
SQL
})
end
is the system avatar needed in the topic list?
it doesn’t give a good feeling to meet a machine-type avatar in the first page, also it doesn’t make sense to change this avatar to a more human-based image.
Yeah I feel the same, I am not sure what avatar to give it though… a simple fix here would be assigning meta system user a nicer avatar.
Maybe Baymax works better, he is certainly softer.
We could also let discobot do the bumping if it exists … which may make more sense here. Will change that tomorrow.
would be awesome 
! knowing that his duty is to take care of the community health!
Earlier today, I wanted to try this new feature and set our support category to 3 topics per day. About 20 minutes later, I realized that this was not a good idea because we have plenty of formally unresolved but de-facto resolved support topics so I turned it off again by setting it to 0 topics per day. However, at the time of writing, we’ve nevertheless had ten (!) old topics bumped.
Am I misunderstanding how this is supposed to work or is this some kind of double bug (it’s not obeying the max of three topics per day and it’s ignoring that I turned if off before the first topic was bumped. We’re on v2.1.0.beta2 +274
We had some issues with this earlier this week, be sure to be on latest … 324 or up…
Is there value in keeping these open forever?
No, but:
So I’d prefer to keep most of them open until it’s easy for people to reply to a closed topic.
Also, we still have a bunch of uncategorized topics from migrating and categorizing those has priority.
So this 2014 topic just got bumped:
https://meta.discourse.org/t/is-there-a-way-to-use-without-an-email-server/15650
Doesn’t feel very useful 
I’d put in a limit on the original posting date, you don’t want to be boosting years old posts.
E.g. only bump posts from the past week or so.