5 replaced http://stackoverflow.com/ with https://stackoverflow.com/
source | link

If you're going to remove the ability to choose a custom off-topic reason, please consider this change on a site-by-site basis, where the site has demonstrated issues or abuse with those reasons. I don't think the concerns you're bringing up will be a problem on smaller or niche sites, while I do acknowledge that they can and will exist on the mother-of-all-SE-sites.

On our site (dba.SE), we mourned the loss of Too localized, as it allowed us to quickly close questions that are not helpful to other users or are simply not welcome. These include:

  • syntax errors (missing bracket, semi-colon, wrong keyword)
  • too localized (how many rows will this affect?)
  • RTFM questions that ask for documentation regurgitation (how does database mirroring work?)

We also still need a way for our users to vote that a question is too simplistic for our site, and that it should get kicked to StackOverflow. They can do this with a custom off-topic reason, but they can't with a canned off-topic reason because the only migration path (for non-moderators) is to our own site's meta.

FWIW we are still finalizing our list of custom off-topic reasons and TL is one of the candidates.

One of the SO questions you said should not have been closed (and is not "too localized") is this one:

http://stackoverflow.com/questions/17323124/sql-join-issue-msg-4145SQL Join Issue - msg 4145

I disagree entirely. That specific error message is actually one that is usually from a different cause, and the missing bracket can often lead to a variety of other messages, depending on where in the query it appears. The question is really "be my second set of eyes and help me debug my code." The number of future users who will make the same typo and lead to the same error message is going to be ridiculously low, and perhaps zero. And I'd rather not have our users spend their time trying to find a duplicate question that was closed as Too Localized before these changes took place when they could still do so. For exampleFor example - and note that the error message here came from a completely different kind of typo.

I do realize that moderators are not always equipped with specific knowledge about a particular technology, and may not recognize the difference between a common issue and one that is way too localized to be useful to others. But don't take away the right for users who are active in the question's tags to identify those same types of questions, and please don't do so network-wide if you're going to do it at all.

If you're going to remove the ability to choose a custom off-topic reason, please consider this change on a site-by-site basis, where the site has demonstrated issues or abuse with those reasons. I don't think the concerns you're bringing up will be a problem on smaller or niche sites, while I do acknowledge that they can and will exist on the mother-of-all-SE-sites.

On our site (dba.SE), we mourned the loss of Too localized, as it allowed us to quickly close questions that are not helpful to other users or are simply not welcome. These include:

  • syntax errors (missing bracket, semi-colon, wrong keyword)
  • too localized (how many rows will this affect?)
  • RTFM questions that ask for documentation regurgitation (how does database mirroring work?)

We also still need a way for our users to vote that a question is too simplistic for our site, and that it should get kicked to StackOverflow. They can do this with a custom off-topic reason, but they can't with a canned off-topic reason because the only migration path (for non-moderators) is to our own site's meta.

FWIW we are still finalizing our list of custom off-topic reasons and TL is one of the candidates.

One of the SO questions you said should not have been closed (and is not "too localized") is this one:

http://stackoverflow.com/questions/17323124/sql-join-issue-msg-4145

I disagree entirely. That specific error message is actually one that is usually from a different cause, and the missing bracket can often lead to a variety of other messages, depending on where in the query it appears. The question is really "be my second set of eyes and help me debug my code." The number of future users who will make the same typo and lead to the same error message is going to be ridiculously low, and perhaps zero. And I'd rather not have our users spend their time trying to find a duplicate question that was closed as Too Localized before these changes took place when they could still do so. For example - and note that the error message here came from a completely different kind of typo.

I do realize that moderators are not always equipped with specific knowledge about a particular technology, and may not recognize the difference between a common issue and one that is way too localized to be useful to others. But don't take away the right for users who are active in the question's tags to identify those same types of questions, and please don't do so network-wide if you're going to do it at all.

If you're going to remove the ability to choose a custom off-topic reason, please consider this change on a site-by-site basis, where the site has demonstrated issues or abuse with those reasons. I don't think the concerns you're bringing up will be a problem on smaller or niche sites, while I do acknowledge that they can and will exist on the mother-of-all-SE-sites.

On our site (dba.SE), we mourned the loss of Too localized, as it allowed us to quickly close questions that are not helpful to other users or are simply not welcome. These include:

  • syntax errors (missing bracket, semi-colon, wrong keyword)
  • too localized (how many rows will this affect?)
  • RTFM questions that ask for documentation regurgitation (how does database mirroring work?)

We also still need a way for our users to vote that a question is too simplistic for our site, and that it should get kicked to StackOverflow. They can do this with a custom off-topic reason, but they can't with a canned off-topic reason because the only migration path (for non-moderators) is to our own site's meta.

FWIW we are still finalizing our list of custom off-topic reasons and TL is one of the candidates.

One of the SO questions you said should not have been closed (and is not "too localized") is this one:

SQL Join Issue - msg 4145

I disagree entirely. That specific error message is actually one that is usually from a different cause, and the missing bracket can often lead to a variety of other messages, depending on where in the query it appears. The question is really "be my second set of eyes and help me debug my code." The number of future users who will make the same typo and lead to the same error message is going to be ridiculously low, and perhaps zero. And I'd rather not have our users spend their time trying to find a duplicate question that was closed as Too Localized before these changes took place when they could still do so. For example - and note that the error message here came from a completely different kind of typo.

I do realize that moderators are not always equipped with specific knowledge about a particular technology, and may not recognize the difference between a common issue and one that is way too localized to be useful to others. But don't take away the right for users who are active in the question's tags to identify those same types of questions, and please don't do so network-wide if you're going to do it at all.

4 replaced http://meta.dba.stackexchange.com/ with https://dba.meta.stackexchange.com/
source | link

If you're going to remove the ability to choose a custom off-topic reason, please consider this change on a site-by-site basis, where the site has demonstrated issues or abuse with those reasons. I don't think the concerns you're bringing up will be a problem on smaller or niche sites, while I do acknowledge that they can and will exist on the mother-of-all-SE-sites.

On our site (dba.SE), we mourned the loss of Too localized, as it allowed us to quickly close questions that are not helpful to other users or are simply not welcome. These include:

  • syntax errors (missing bracket, semi-colon, wrong keyword)
  • too localized (how many rows will this affect?)
  • RTFM questions that ask for documentation regurgitation (how does database mirroring work?)

We also still need a way for our users to vote that a question is too simplistic for our site, and that it should get kicked to StackOverflow. They can do this with a custom off-topic reason, but they can't with a canned off-topic reason because the only migration path (for non-moderators) is to our own site's meta.

FWIW we are still finalizing our list of custom off-topic reasonswe are still finalizing our list of custom off-topic reasons and TL is one of the candidates.

One of the SO questions you said should not have been closed (and is not "too localized") is this one:

http://stackoverflow.com/questions/17323124/sql-join-issue-msg-4145

I disagree entirely. That specific error message is actually one that is usually from a different cause, and the missing bracket can often lead to a variety of other messages, depending on where in the query it appears. The question is really "be my second set of eyes and help me debug my code." The number of future users who will make the same typo and lead to the same error message is going to be ridiculously low, and perhaps zero. And I'd rather not have our users spend their time trying to find a duplicate question that was closed as Too Localized before these changes took place when they could still do so. For example - and note that the error message here came from a completely different kind of typo.

I do realize that moderators are not always equipped with specific knowledge about a particular technology, and may not recognize the difference between a common issue and one that is way too localized to be useful to others. But don't take away the right for users who are active in the question's tags to identify those same types of questions, and please don't do so network-wide if you're going to do it at all.

If you're going to remove the ability to choose a custom off-topic reason, please consider this change on a site-by-site basis, where the site has demonstrated issues or abuse with those reasons. I don't think the concerns you're bringing up will be a problem on smaller or niche sites, while I do acknowledge that they can and will exist on the mother-of-all-SE-sites.

On our site (dba.SE), we mourned the loss of Too localized, as it allowed us to quickly close questions that are not helpful to other users or are simply not welcome. These include:

  • syntax errors (missing bracket, semi-colon, wrong keyword)
  • too localized (how many rows will this affect?)
  • RTFM questions that ask for documentation regurgitation (how does database mirroring work?)

We also still need a way for our users to vote that a question is too simplistic for our site, and that it should get kicked to StackOverflow. They can do this with a custom off-topic reason, but they can't with a canned off-topic reason because the only migration path (for non-moderators) is to our own site's meta.

FWIW we are still finalizing our list of custom off-topic reasons and TL is one of the candidates.

One of the SO questions you said should not have been closed (and is not "too localized") is this one:

http://stackoverflow.com/questions/17323124/sql-join-issue-msg-4145

I disagree entirely. That specific error message is actually one that is usually from a different cause, and the missing bracket can often lead to a variety of other messages, depending on where in the query it appears. The question is really "be my second set of eyes and help me debug my code." The number of future users who will make the same typo and lead to the same error message is going to be ridiculously low, and perhaps zero. And I'd rather not have our users spend their time trying to find a duplicate question that was closed as Too Localized before these changes took place when they could still do so. For example - and note that the error message here came from a completely different kind of typo.

I do realize that moderators are not always equipped with specific knowledge about a particular technology, and may not recognize the difference between a common issue and one that is way too localized to be useful to others. But don't take away the right for users who are active in the question's tags to identify those same types of questions, and please don't do so network-wide if you're going to do it at all.

If you're going to remove the ability to choose a custom off-topic reason, please consider this change on a site-by-site basis, where the site has demonstrated issues or abuse with those reasons. I don't think the concerns you're bringing up will be a problem on smaller or niche sites, while I do acknowledge that they can and will exist on the mother-of-all-SE-sites.

On our site (dba.SE), we mourned the loss of Too localized, as it allowed us to quickly close questions that are not helpful to other users or are simply not welcome. These include:

  • syntax errors (missing bracket, semi-colon, wrong keyword)
  • too localized (how many rows will this affect?)
  • RTFM questions that ask for documentation regurgitation (how does database mirroring work?)

We also still need a way for our users to vote that a question is too simplistic for our site, and that it should get kicked to StackOverflow. They can do this with a custom off-topic reason, but they can't with a canned off-topic reason because the only migration path (for non-moderators) is to our own site's meta.

FWIW we are still finalizing our list of custom off-topic reasons and TL is one of the candidates.

One of the SO questions you said should not have been closed (and is not "too localized") is this one:

http://stackoverflow.com/questions/17323124/sql-join-issue-msg-4145

I disagree entirely. That specific error message is actually one that is usually from a different cause, and the missing bracket can often lead to a variety of other messages, depending on where in the query it appears. The question is really "be my second set of eyes and help me debug my code." The number of future users who will make the same typo and lead to the same error message is going to be ridiculously low, and perhaps zero. And I'd rather not have our users spend their time trying to find a duplicate question that was closed as Too Localized before these changes took place when they could still do so. For example - and note that the error message here came from a completely different kind of typo.

I do realize that moderators are not always equipped with specific knowledge about a particular technology, and may not recognize the difference between a common issue and one that is way too localized to be useful to others. But don't take away the right for users who are active in the question's tags to identify those same types of questions, and please don't do so network-wide if you're going to do it at all.

3 added 204 characters in body
source | link

If you're going to remove the ability to choose a custom off-topic reason, please consider this change on a site-by-site basis, where the site has demonstrated issues or abuse with those reasons. I don't think the concerns you're bringing up will be a problem on smaller or niche sites, while I do acknowledge that they can and will exist on the mother-of-all-SE-sites.

On our site (dba.SE), we mourned the loss of Too localized, as it allowed us to quickly close questions that are not helpful to other users or are simply not welcome. These include:

  • syntax errors (missing bracket, semi-colon, wrong keyword)
  • too localized (how many rows will this affect?)
  • RTFM questions that ask for documentation regurgitation (how does database mirroring work?)

We also still need a way for our users to vote that a question is too simplistic for our site, and that it should get kicked to StackOverflow. They can do this with a custom off-topic reason, but they can't with a canned off-topic reason because the only migration path (for non-moderators) is to our own site's meta.

FWIW we are still finalizing our list of custom off-topic reasons and TL is one of the candidates.

One of the SO questions you said should not have been closed (and is not "too localized") is this one:

http://stackoverflow.com/questions/17323124/sql-join-issue-msg-4145

I disagree entirely. That specific error message is actually one that is usually from a different cause, and the missing bracket can often lead to a variety of other messages, depending on where in the query it appears. The question is really "be my second set of eyes and help me debug my code." The number of future users who will make the same typo and lead to the same error message is going to be ridiculously low, and perhaps zero. And I'd rather not have our users spend their time trying to find a duplicate question that was closed as Too Localized before these changes took place when they could still do so. For example - and note that the error message here came from a completely different kind of typo.

I do realize that moderators are not always equipped with specific knowledge about a particular technology, and may not recognize the difference between a common issue and one that is way too localized to be useful to others. But don't take away the right for users who are active in the question's tags to identify those same types of questions, and please don't do so network-wide if you're going to do it at all.

If you're going to remove the ability to choose a custom off-topic reason, please consider this change on a site-by-site basis, where the site has demonstrated issues or abuse with those reasons. I don't think the concerns you're bringing up will be a problem on smaller or niche sites, while I do acknowledge that they can and will exist on the mother-of-all-SE-sites.

On our site (dba.SE), we mourned the loss of Too localized, as it allowed us to quickly close questions that are not helpful to other users or are simply not welcome. These include:

  • syntax errors (missing bracket, semi-colon, wrong keyword)
  • too localized (how many rows will this affect?)
  • RTFM questions that ask for documentation regurgitation (how does database mirroring work?)

We also still need a way for our users to vote that a question is too simplistic for our site, and that it should get kicked to StackOverflow. They can do this with a custom off-topic reason, but they can't with a canned off-topic reason because the only migration path (for non-moderators) is to our own site's meta.

One of the SO questions you said should not have been closed (and is not "too localized") is this one:

http://stackoverflow.com/questions/17323124/sql-join-issue-msg-4145

I disagree entirely. That specific error message is actually one that is usually from a different cause, and the missing bracket can often lead to a variety of other messages, depending on where in the query it appears. The question is really "be my second set of eyes and help me debug my code." The number of future users who will make the same typo and lead to the same error message is going to be ridiculously low, and perhaps zero. And I'd rather not have our users spend their time trying to find a duplicate question that was closed as Too Localized before these changes took place when they could still do so. For example - and note that the error message here came from a completely different kind of typo.

I do realize that moderators are not always equipped with specific knowledge about a particular technology, and may not recognize the difference between a common issue and one that is way too localized to be useful to others. But don't take away the right for users who are active in the question's tags to identify those same types of questions, and please don't do so network-wide if you're going to do it at all.

If you're going to remove the ability to choose a custom off-topic reason, please consider this change on a site-by-site basis, where the site has demonstrated issues or abuse with those reasons. I don't think the concerns you're bringing up will be a problem on smaller or niche sites, while I do acknowledge that they can and will exist on the mother-of-all-SE-sites.

On our site (dba.SE), we mourned the loss of Too localized, as it allowed us to quickly close questions that are not helpful to other users or are simply not welcome. These include:

  • syntax errors (missing bracket, semi-colon, wrong keyword)
  • too localized (how many rows will this affect?)
  • RTFM questions that ask for documentation regurgitation (how does database mirroring work?)

We also still need a way for our users to vote that a question is too simplistic for our site, and that it should get kicked to StackOverflow. They can do this with a custom off-topic reason, but they can't with a canned off-topic reason because the only migration path (for non-moderators) is to our own site's meta.

FWIW we are still finalizing our list of custom off-topic reasons and TL is one of the candidates.

One of the SO questions you said should not have been closed (and is not "too localized") is this one:

http://stackoverflow.com/questions/17323124/sql-join-issue-msg-4145

I disagree entirely. That specific error message is actually one that is usually from a different cause, and the missing bracket can often lead to a variety of other messages, depending on where in the query it appears. The question is really "be my second set of eyes and help me debug my code." The number of future users who will make the same typo and lead to the same error message is going to be ridiculously low, and perhaps zero. And I'd rather not have our users spend their time trying to find a duplicate question that was closed as Too Localized before these changes took place when they could still do so. For example - and note that the error message here came from a completely different kind of typo.

I do realize that moderators are not always equipped with specific knowledge about a particular technology, and may not recognize the difference between a common issue and one that is way too localized to be useful to others. But don't take away the right for users who are active in the question's tags to identify those same types of questions, and please don't do so network-wide if you're going to do it at all.

2 added 85 characters in body
source | link
1
source | link