<p>I am really concerned that this will prevent people from asking questions or getting help on stack exchange.  Here are my reasons:</p>

<ol>
<li><strong>Sythesis Questions:</strong> On rare occassions, I have re-asked a question to get a sythesis or concluding answer. I do this because the question has no definitive (well-defined) answer either because of the following reasons below:</li>
</ol>

<blockquote>
  <ol>
  <li>The answer changed over the years over the multiple times it has been asked</li>
  <li>It has been asked with so many different variations and these variations have completely different answers </li>
  <li>It has been answered in a non-direct means often with extra-enous information</li>
  </ol>
</blockquote>

<ol>
<li><strong>Potential for Overfitting</strong> It will take a long time for accuracy and precision to be good enough to avoid overfitting and be able to release it into the wild.  How do I know there will be overfitting? Well, I personally have noticed that suggested answers for coding on stack overflow do not match up well usually with the questions I am asking while I am typing it. Considering how this question matching algorithm performs on stack exchange, I think this shows that the unstructured data from stack exchange posts is prone to overfitting and we have to be careful of that.</li>
<li><strong>Skewed toward/against the questions of new users</strong>: Depending on how you code it the algorithm is going to be skewed toward or against news users in a signficant way.  Right now my guess is toward new users; however, I want to show both because we have to be aware of it.  I think you need to closely monitor growth new users on stack exchange to make sure there is not a significant drop in activity as you more you automate this process.

<blockquote>
  <ol>
  <li>[Reason for the skew against] Basically new users are prone toward producing missing values this text mined dataset then older users because reputation system promotes such behavior. Consider for a minute on what @Glen_b pointed out with the [0] and the misspelled name.  Do you think that these syntax errors are random human error? No, they are intentional and have non-random reasons much like the missing values or  you might find in a database. The major reason the person probably misspelled it the way he did was because of stack exchange limits both the content and type of questions new users can ask especially well documented questions.  Personally, I cannot tell you the number of times I have had misspell or format a question/answers in an odd way just so I can keep my references while getting around the reference limit from the subjective filter, link limit, spam filter (Not the actual question text but the actual references themselves). </li>
  <li>[Reason for the Skew Toward] On the other hand, new users are less familiar with the site are more prone not to be familar with how to navigate stack exchange and thus will ask duplicated questions.</li>
  </ol>
</blockquote></li>
<li><strong>StackOverflow will be an outlier in performance</strong>:  In terms of behavior of the algorithm I think we can predicted that stack overflow will be an outlier for two major reasons: 1) There is a lack of good syntax thesaurus between the top 5 most popular languages.  So to ask how to code something in one language means there are at least 5 valid duplicates of how to code that in a different language.  2) The dependency on tags as classifier, cluster, or filter of question @IanRingrose mentioned.  So it either going to perform really well for stackoverflow or really poorly for stackoverflow.</li>
</ol>

<p>The duplicate questions tag does not automatically delete questions, so Synthesis Questions, Overfitting, and Outliers are currently dealt with because people can object to having a closed thread or duplicate tag.  I am worried that this safe guard from duplicate questions tag will be removed when one releases Project Reduplication of Deduplication into the full wild of stack overflow.</p>

<p>P.S. Also I just posted an example of reason 1.2 (Synthesis Question) in Cross Validated</p>
