Return to Answer

##I don't completely agree with this policy.

• ##Find the best location for your question.

  There are a lot of StackExchange sites, some more active than others. Remember that activity is a double-edged sword. For example, questions on the front-page of StackOverflow are on the second page within a few minutes. On a slower, site, even if there are fewer users, more people might see your question.

• ##If you do cross-post, cross-link them!

  Child posts should have links to the original post and if you can, try to keep the parent posts updated with a list of places you've cross-posted it to. This means that users of any site can quickly see if there have been any answers. Or post their answer on the main thread.

  If you're honest and up-front about it, we [moderators] are going to get fewer flags about it. People can track things and see if your other thread has any answers.

• ##Update all your threads as soon as one gets a result.

  This is probably the most important point. They you're questions so it's your responsibility to tell users on all the sites when you no longer need help. Doing this means they're not going to waste time fixing something that is already fixed.

  Do this by either answering your own question with a link to the other answer, or in the case of IRC, say what's happened, giving the user credit. Chances are you won't be able to accept your own question if you're answering it yourself, so just flag it up and we can close it for you.

  Yes, this is more work for you but that's the cost of responsible cross-posting.

I don't completely agree with this policy.

• Find the best location for your question.

  There are a lot of StackExchange sites, some more active than others. Remember that activity is a double-edged sword. For example, questions on the front-page of StackOverflow are on the second page within a few minutes. On a slower, site, even if there are fewer users, more people might see your question.

• If you do cross-post, cross-link them!

  Child posts should have links to the original post and if you can, try to keep the parent posts updated with a list of places you've cross-posted it to. This means that users of any site can quickly see if there have been any answers. Or post their answer on the main thread.

  If you're honest and up-front about it, we [moderators] are going to get fewer flags about it. People can track things and see if your other thread has any answers.

• Update all your threads as soon as one gets a result.

  This is probably the most important point. They you're questions so it's your responsibility to tell users on all the sites when you no longer need help. Doing this means they're not going to waste time fixing something that is already fixed.

  Do this by either answering your own question with a link to the other answer, or in the case of IRC, say what's happened, giving the user credit. Chances are you won't be able to accept your own question if you're answering it yourself, so just flag it up and we can close it for you.

  Yes, this is more work for you but that's the cost of responsible cross-posting.

I personally don't have anything against it if it's done well but the official Stack Exchange policy on intra-StackExchange cross-posting is more clear on the topic:

I personally don't have anything against it if it's done well but the official Stack Exchange policy on intra-StackExchange cross-posting is more clear on the topic:

I don't completely agree with this policy.

I think I'd be a massive hypocrite if I slammed every cross-posted question as some sort of Simpsons-did-it-first-duplicate. What makes two diverse StackExchange sites more "special" than disconnected support avenues like Ask Ubuntu is to Ubuntu Forums or IRC? The same mechanics apply: you ask for help; people invest time to help you; you win.

• Find the best location for your question.

  There are a lot of StackExchange sites, some more active than others. Remember that activity is a double-edged sword. For example, questions on the front-page of StackOverflow are on the second page within a few minutes. On a slower, site, even if there are fewer users, more people might see your question.

• If you do cross-post, cross-link them!

  Child posts should have links to the original post and if you can, try to keep the parent posts updated with a list of places you've cross-posted it to. This means that users of any site can quickly see if there have been any answers. Or post their answer on the main thread.

  If you're honest and up-front about it, we [moderators] are going to get fewer flags about it. People can track things and see if your other thread has any answers.

• Update all your threads as soon as one gets a result.

  This is probably the most important point. They you're questions so it's your responsibility to tell users on all the sites when you no longer need help. Doing this means they're not going to waste time fixing something that is already fixed.

  Do this by either answering your own question with a link to the other answer, or in the case of IRC, say what's happened, giving the user credit. Chances are you won't be able to accept your own question if you're answering it yourself, so just flag it up and we can close it for you.

  Yes, this is more work for you but that's the cost of responsible cross-posting.

##I don't completely agree with this policy.

I think I'd be a massive hypocrite if I slammed every cross-posted question as some sort of Simpsons-did-it-first-duplicate. What makes two diverse StackExchange sites more "special" than disconnected support avenues like Ask Ubuntu is to Ubuntu Forums or IRC? The same mechanics apply: you ask for help; people invest time to help you; you win.

• ##Find the best location for your question.

  There are a lot of StackExchange sites, some more active than others. Remember that activity is a double-edged sword. For example, questions on the front-page of StackOverflow are on the second page within a few minutes. On a slower, site, even if there are fewer users, more people might see your question.

   

• ##If you do cross-post, cross-link them!

  Child posts should have links to the original post and if you can, try to keep the parent posts updated with a list of places you've cross-posted it to. This means that users of any site can quickly see if there have been any answers. Or post their answer on the main thread.

  If you're honest and up-front about it, we [moderators] are going to get fewer flags about it. People can track things and see if your other thread has any answers.

   

• ##Update all your threads as soon as one gets a result.

  This is probably the most important point. They you're questions so it's your responsibility to tell users on all the sites when you no longer need help. Doing this means they're not going to waste time fixing something that is already fixed.

  Do this by either answering your own question with a link to the other answer, or in the case of IRC, say what's happened, giving the user credit. Chances are you won't be able to accept your own question if you're answering it yourself, so just flag it up and we can close it for you.

  Yes, this is more work for you but that's the cost of responsible cross-posting.