Detect Duplicate Questions
Once upon a time, there was a golfing site. It had a problem: people would post similar or identical questions again and again. You have been
chosen selected forced conscripted blackmailed requested to automate the process of deciding whether a question is a duplicate of an existing one, by whatever means necessary (see Rules).
Your program must accept a single URL as input. It may assume that this leads to a question on codegolf.stackexchange.com.
Search the site for similar questions. If you think that the input question is a duplicate of an existing question (or vice versa), output the other question's URL. You may output multiple URLs, separated by new lines. At the end of your output, output
end (on a separate line).
- If a question that you output was indeed marked as a duplicate of the input question (or vice versa), you score 4 points. This is a "correct guess".
- For each false positive (aka "incorrect guess"), you lose 2 points.
- For each question that was actually a duplicate but does not appear in your output (aka "missing guess"), lose 1 point.
The highest score after handling 32 input questions wins. These 32 questions are a "round". At the beginning of each round, the scores will be reset to 0. One round will be run every few days, and the leaderboard updated after each round.
- If questions A and C are both closed as duplicates of B, A will count as a duplicate of C and vice versa.
- At the start of each round, your program may not possess any data about any questions (i.e. no hardcoding), except on how to parse the website.
- However, you may keep data in external files during a round.
- No data may be kept between rounds.
- Your output must have a trailing new line.
- You may not use any data from the website except search results and the URL, title, tags and text of a question, with or without formatting. For example, you may not use the text "marked as duplicate by foo, bar..." that appears on duplicate questions.
- You may retrieve this data directly from the site, via data.SE or via the API.
- Each submission must have a name.
- Each submission must have clear version numbering.
- If a submission does not produce output after a time limit (to be decided; please state how long your submission takes) it will be killed and lose 8 points.