Return to Answer

As you note, there's a site setting that CMs/devs can adjust to prevent the Community user from bumping a post if another post has recently been bumped. Specifically, this site setting lets us specify a custom value such that the Community user will not bump posts if at least one in the top N, sorted by activity date, has been bumped. (By default, this setting is not enabled.)

These are the sites that have this setting enabled (with N set to the specified value):

1. Android (set to 5), as a result of this request
2. ExpressionEngine (set to 5), following this post on their Meta
3. Game Development (set to 5), as a result of this request
4. Hardware Recommendations (set to 5), as a result of this post on MSE
5. Server Fault (set to 5), as a result of this request
6. Stack Overflow in Japanese (set to 5), following this request
7. Tor (set to 10) – no request on their Meta, but a CM enabled this due to the site's front page being mostly Community-bumped posts (as a result of low activity on the site)

(For reference, there's also a different site setting that controls the maximum number of questions that Community can bump per hour; the default value is 1.)

As you note, there's a site setting that CMs/devs can adjust to prevent the Community user from bumping a post if another post has recently been bumped. Specifically, this site setting lets us specify a custom value such that the Community user will not bump posts if at least one in the top N, sorted by activity date, has been bumped. (By default, this setting is not enabled.)

These are the sites that have this setting enabled (with N set to the specified value):

1. Android (set to 5), as a result of this request
2. ExpressionEngine (set to 5), following this post on their Meta
3. Game Development (set to 5), as a result of this request
4. Hardware Recommendations (set to 5), as a result of this post on MSE
5. Server Fault (set to 5), as a result of this request
6. Stack Overflow in Japanese (set to 5), following this request
7. Tor (set to 10) – no request on their Meta, but a CM enabled this due to the site's front page being mostly Community-bumped posts (as a result of low activity on the site)

(For reference, there's also a different site setting that controls the maximum number of questions that Community can bump per hour; the default value is 1.)

As you note, there's a site setting that CMs/devs can adjust to prevent the Community user from bumping a post if another post has recently been bumped. Specifically, this site setting lets us specify a custom value such that the Community user will not bump posts if at least one in the top N, sorted by activity date, has been bumped. (By default, this setting is not enabled.)

There are currently 6 sites that have this setting enabled (with N set to the specified value):

• Android (set to 5), as a result of this request
• ExpressionEngine (set to 5), following this post on their Meta
• Game Development (set to 5), as a result of this request
• Hardware Recommendations (set to 5), as a result of this post on MSE
• Server Fault (set to 5), as a result of this request
• Stack Overflow in Japanese (set to 5), following this request
• Tor (set to 10) – no request on their Meta, but a CM enabled this due to the site's front page being mostly Community-bumped posts (as a result of low activity on the site)

(For reference, there's also a different site setting that controls the maximum number of questions that Community can bump per hour; the default value is 1.)

As you note, there's a site setting that CMs/devs can adjust to prevent the Community user from bumping a post if another post has recently been bumped. Specifically, this site setting lets us specify a custom value such that the Community user will not bump posts if at least one in the top N, sorted by activity date, has been bumped. (By default, this setting is not enabled.)

These are the sites that have this setting enabled (with N set to the specified value):

1. Android (set to 5), as a result of this request
2. ExpressionEngine (set to 5), following this post on their Meta
3. Game Development (set to 5), as a result of this request
4. Hardware Recommendations (set to 5), as a result of this post on MSE
5. Server Fault (set to 5), as a result of this request
6. Stack Overflow in Japanese (set to 5), following this request
7. Tor (set to 10) – no request on their Meta, but a CM enabled this due to the site's front page being mostly Community-bumped posts (as a result of low activity on the site)

(For reference, there's also a different site setting that controls the maximum number of questions that Community can bump per hour; the default value is 1.)

As you note, there's a site setting that CMs/devs can adjust to prevent the Community user from bumping a post if another post has recently been bumped. Specifically, this site setting lets us specify a custom value such that the Community user will not bump posts if at least one in the top N, sorted by activity date, has been bumped. (By default, this setting is not enabled.)

There are currently 6 sites that have this setting enabled (with N set to the specified value):

• Android (set to 5), as a result of this request
• ExpressionEngine (set to 5), following this post on their Meta
• Game Development (set to 5), as a result of this request
• Hardware Recommendations (set to 5), as a result of this post on MSE
• Server Fault (set to 5), as a result of this request
• Stack Overflow in Japanese (set to 5), following this request
• Tor (set to 10) – no request on their Meta, but a CM enabled this due to the site's front page being mostly Community-bumped posts (as a result of low activity on the site)

(For reference, there's also a different site setting that controls the maximum number of questions that Community can bump per hour; the default value is 1.)

As you note, there's a site setting that CMs/devs can adjust to prevent the Community user from bumping a post if another post has recently been bumped. Specifically, this site setting lets us specify a custom value such that the Community user will not bump posts if at least one in the top N, sorted by activity date, has been bumped. (By default, this setting is not enabled.)

There are currently 6 sites that have this setting enabled (with N set to the specified value):

• Android (set to 5), as a result of this request
• ExpressionEngine (set to 5), following this post on their Meta
• Game Development (set to 5), as a result of this request
• Hardware Recommendations (set to 5), as a result of this post on MSE
• Server Fault (set to 5), as a result of this request
• Stack Overflow in Japanese (set to 5), following this request
• Tor (set to 10) – no request on their Meta, but a CM enabled this due to the site's front page being mostly Community-bumped posts (as a result of low activity on the site)

(For reference, there's also a different site setting that controls the maximum number of questions that Community can bump per hour; the default value is 1.)