What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 134 Stack Exchange communities.

I realize that tweeting questions by @serverfault (and other SE twitter accounts) is automated, but shouldn't questions with close votes not be tweeted?

For example this is way OT for SF and has 4 close votes at the time of this writing. It had (I believe) two close votes when it was tweeted.

enter image description here

I don't know what the algorithm for tweeting questions is, but this question wasn't highly voted, it was very new, it had close votes, and it's from a low-rep user. Maybe it's time to be a little more selective?

If my memory is failing me and this was tweeted before close votes, my premise still stands. The question is about 40 minutes old at the time of this writing and was tweeted about 4 minutes after it was asked. Shouldn't questions be given enough time to be vetted by the community before they're shouted to the twitter universe?

share|improve this question
19  
My subjective impression is that the algorithm is optimized for tweeting bad question just a minute before they are closed. –  Mad Scientist Dec 12 '11 at 14:58
    
Could what is really happening here be that Tweeting the questions is causing the close votes, by virtue of the additional attention? –  Andrew Barber Dec 12 '11 at 15:10
6  
@AndrewBarber Even if that's the case, this question was tweeted when it was ~4 minutes old. Shouldn't the community be given the chance to close the crap before it gets tweeted? –  MDMarra Dec 12 '11 at 15:11
10  
In either case, it creates a bad impression for the site if bad questions are tweeted, not just because they're then closed but because they're bad questions, and therefore not a good advert for the site in the first place. –  RobM Dec 12 '11 at 15:27
1  
1  
related: Avoid sharing bad questions at Facebook –  gnat Nov 26 at 22:19
    
-1 the closevotes might be wrong ... –  Dilaton Nov 26 at 22:44
    
@Dilaton sure, and so might downvotes or answers or upvotes. Why don't we do away with all of it? –  MDMarra Nov 26 at 22:45

1 Answer 1

up vote 27 down vote accepted

This is now deployed...we won't tweet questions with close votes (with the exception of bounties, which we feel didn't need this check...they survived around long enough for the bounty to start).

share|improve this answer
2  
Even with a single close vote? I've noticed at least on UX.SE a single close vote is reasonably easy to get. By the time you have 3 it's probably a bad question. –  Ben Brocka Jan 6 '12 at 22:40
4  
@Ben - Yes, even a single close vote...better to be safe here, since on some sites it's hard to even get 1 close vote, we'd rather err on the side of caution when publicizing content. –  Nick Craver Jan 7 '12 at 1:36
    
Makes sense, I don't really oppose it –  Ben Brocka Jan 7 '12 at 1:41
4  
Does it look at flags on the question as well? If not can it and not Tweet anything with a flag. Thank you very much. –  ChrisF Mar 7 '12 at 21:59
2  
@NickCraver: Yeah, what about flags? –  Dynamic Mar 9 '12 at 20:35
    
You guys should probably also check out this one here – wonder how that got tweeted. –  slhck May 5 '12 at 21:49
    
What if the closevoters are wrong? At least on physics SE there is a bunch of closevoters and batch hunters who regularly overreaches their state of knowledge by going on a closevote spree against high-level technical questions they have no clue about. The bad impact of thouse people should not be amplified by making their bad capricious closevotes prevent that legitimate up to very good questions get shared ... I dont know if other sites know this problem too. –  Dilaton Nov 26 at 22:42
    
Why is that relevant here @Dilaton? If we assume what you say is true, then the problem is the capricious closevotes, not the tweet script. And that's a problem only the Physics.SE community can solve... –  Yannis Nov 27 at 13:11

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .