So we've established that it's appropriate for meta to contain questions that aren't really answerable. Which suggests that the algorithm whereby Community♦ randomly bumps questions without accepted answers to the top of the list might not be a particularly good idea in meta.

Case in point: podcast #2 was just bumped to the top of meta. Really? enter image description here

  • 3
    I don't know whether this is a bug, a feature request, or a "feature" removal request. – Daniel Mod Feb 4 '12 at 22:43
  • 1
    Feature request, IMO. Community ♦ is doing it's intended behavior, behavior I don't think it should have on any meta site. (At least not by default. If someone thinks it should be on a meta, that should be their exception, not the rule.) – Jason Salaz Feb 6 '12 at 7:11
  • 1
    Where is the list of what and how apple.stackexchange.com/users/-1 (aka Community ♦) does it's tasks? Sometimes I'd ask it to just go calculate the square root of it's user number and come back when it has an answer. – bmike Mod Mar 1 '12 at 15:54
  • It just has to use its imagination, @bmike, and the answer's easy. – Daniel Mod Mar 1 '12 at 15:56
  • Someone downvoted this -- if you just think this isn't a priority, great, but if you have an argument why it's actually desirable to randomly bump unanswered posts on meta, please do respond; I'd love to hear the argument. – Daniel Mod Mar 1 '12 at 17:32
  • 1
    If no one ever answers this, it can be performance art by @community – bmike Mod Sep 30 '13 at 23:46

You must log in to answer this question.

Browse other questions tagged .