Skip to main content

Timeline for Duplicate questions

Current License: CC BY-SA 3.0

13 events
when toggle format what by license comment
Mar 16, 2017 at 15:46 history edited CommunityBot
replaced http://meta.codegolf.stackexchange.com/ with https://codegolf.meta.stackexchange.com/
Mar 16, 2017 at 15:46 history edited CommunityBot
replaced http://meta.codegolf.stackexchange.com/ with https://codegolf.meta.stackexchange.com/
Aug 30, 2014 at 13:38 comment added Kyle Kanos @Ryan: So it appears your saying that all of these points are just a cover for wanting to farm rep. this is how I am interpreting the positions here. By wanting new copies of the same challenge, you want the exposure to earn more rep, rather than wanting the challenge of stripping down your code as much as possible (or in some cases, learning a new language). I honestly do not see how you can argue that your position is anything but this.
Aug 30, 2014 at 10:59 comment added Kyle Kanos @Ryan: I did read the post, so I'm well aware that rep farming wasn't mentioned (so your statement is superfluous), but it was my first thought when I read this post. I also don't say anything about how someone wanting the challenge should vote, so please do not try putting words in my mouth. My point is that there are duplicates and only people interested in farming rep want to keep it open instead of going back to the old one (xnor even says, chance are barely anyone will see it. You might as well submit it to dev/null. Likewise for edits to improve an old challenge.).
Aug 29, 2014 at 19:16 comment added Peter Taylor There are four ways to bring attention to an old challenge: chat, bounty, posting your own answer, and posting a dupe. Only the last one has broken incentives like encouraging people to repost their earlier answers in the hope of farming more rep. And if it's community agreement and the social aspects that you're looking for then drumming up interest in chat is a better solution than posting a dupe.
Aug 29, 2014 at 19:16 comment added Peter Taylor The scenario you pose is the exception, not the rule. My thoughts on it are expressed in more detail elsewhere, but basically it's a lose-lose situation. However, to the more common case where the dupe isn't an obvious improvement over the older question, you're overstating your case. "Anyone who was not on the site at the time misses out on that topic forever" is just not true.
Aug 29, 2014 at 13:00 comment added Kyle Kanos If you want more rep (farming), you don't want closed questions because it means less opportunity to get said rep. If you want challenges, then it doesn't matter that you answer an old post (and get little/no rep) but it's in your best interest to eliminate duplicates. That's just my take on it.
Aug 29, 2014 at 2:15 comment added xnor @KyleKanos I'm confused then. What do close votes have to do with rep?
Aug 29, 2014 at 2:09 comment added Kyle Kanos Please read my comment again. I am not accusing anyone of farming rep, it is part of the dichotomy that I see (either you want the rep & should vote accordingly or you want the challenge and vote accordingly).
Aug 29, 2014 at 2:03 comment added xnor @KyleKanos I think the accusation of rep farming is totally unfair. People want to participate in challenges with other golfers; that's the point of the community. Of course the point is the challenge, but you too choose to post your golfs rather than leaving them on your computer for your private satisfaction.
Aug 29, 2014 at 1:07 comment added Kyle Kanos If your goal is to farm rep, then by all means vote to keep every post open. If, however, your goal is to challenge yourself to solve problems in as short a code as possible, then who cares that you might or might not get an upvote? The want is the challenge, not the rep. Note also that the main page (codegolf.stackexchange.com) shows all posts (with score > -3) that have been edited or answered, so chances are the many of us who watch that will see the new answer.
Aug 28, 2014 at 19:11 history edited xnor CC BY-SA 3.0
deleted 5 characters in body
Aug 28, 2014 at 19:05 history answered xnor CC BY-SA 3.0