Link-only answers are never fine.
If you need to link to a SuperUser question or answer in order to answer a question, vote or flag to close the question as a duplicate of that question.
If linking to the other question does not provide enough information, but you want to provide the same type of answer to express that it's one possible way of doing that, ...
When a "duplicate" close vote or flag is cast, a box appears above the question visible to the question's owner. It prompts the author to either edit the question to clarify its non-duplicateness or accept the duplicity by pressing a "yes, that solved my problem" button. If the user chooses that button, the Community user casts the final duplicate vote, ...
If there's another answer added
much later than an already existing one, and it's
absolutely the same as another answer, content-wise
then there's rarely need to keep redundant information around.
I wouldn't call out users for posting duplicate answers – it's probably just because they haven't read the other answers or feel the need to add their two cents,...
Someone went and edited the duplicate close banner, which normally shouldn't be able to happen. The problem in this case is that the question was closed before the current system was put in place and the the banner was handled differently back then.
I have edited it and re-closed it to fix the duplicate banner.
The way to go about reporting this is either ...
If the questions are duplicates, one should be closed as such. In that case, it should be explained to the user that we prefer information to be centralized, so they should flag instead of posting the same answer to both. Once the duplicate question relationship is established, one of the duplicate answers can be deleted. Those two questions look pretty ...
There's nothing legally wrong with copying an answer wholesale, provided there's clear attribution. Content creators agreed to those guidelines when they posted on a Stack Exchange site. That said, I'm not sure that copying in other sites' answers is the best thing to do.
If a certain topic is acceptable at multiple Stack Exchange sites, there's a good ...
In the end what matters is giving our users better answers. Given the question wasn't closed as a dupe before getting better answers, I'd say the order is no longer important.
So I'd say yes: close the question with the inferior answers as a dupe of the question with superior answers or leave them both open if they are sufficiently distinct.
Post it as new question?
This is the correct action to take, as it will give your problem the visibility it needs in order to get an answer.
You should ask a new question, referencing the old one if appropriate.
Comment in the original, answered question?
Asking in a comment on an old answer to the old question is problematic because:
The person who ...
If you don't have a lot of time but want to be helpful:
Comment on the question, leaving a link to the older question
Otherwise, I'd go for:
Quote that answer (or reword it, possibly making it more valuable) and flag older (more specific) question as a duplicate
Generally, links to other posts on Super User are not as prone to link rot as external ...
It seems as though some users on Stack Exchange are a bit trigger-happy
when it comes to closing questions.
Somebody asks "How do I do X on Windows 10?", and it gets closed
as a duplicate of "How do I do X on Windows 7?"
Or Solaris and Linux.
Or bash and zsh.
And the talking heads come out and say, "Well, it's the same question.
If those answers don't ...
One option: Vote to close the original question instead. If its information is no longer current, and the newer question and answers to it have been posted anyway, make the newer question the "original". Could single, still applicable answers be moved to the newer question? Or will merging always merge into the older topic?
This invites participation on the ...
Can I edit other questions because of this?
First things first:
Can I add more points to the question? So the duplicity can be reduced and all the readers can answer a single question perfectly.
If you're talking about the duplicates: Please don't do that, unless you also change all the answers (cough please don't do that either cough). If your question ...
Sounds like it's time for a community-faq!
The purpose of a Community FAQ is to provide a comprehensive, detailed, generic canonical post on a frequently asked subject. Check out other questions in this tag for examples.
I think a "how to dual-boot linux and Windows" post, with a basic how-to and some more detailed info about specific common edge cases ...
No. If its your own question, a bounty is the right way, assuming you have the reputation. If you want to add more helpful, relevant details, go ahead (Thats to say, don't edit to bump. Edit to include more relevant information).
If its a related tangential question, sufficiently distinct to warrant its own question, you can refer back to the old one, but ...
As far as I know, excerpts of already posted answers are ok as long as they respect original authorship, e.g. including a link to the original answer.
If the newer answers are blatant copies (which in my opinion also involves the case you mention) of existing answers, I'd flag for moderator attention explaining this is a copy of an already posted answer so ...
What would be the best approach here (1 or 2)?
What if I disagree with the closure of a question? How can I reopen it?
Stack Exchange is collaboratively built, maintained, and moderated by
the community. If you see a question and you disagree with the stated
reason of its closure, you should first try to edit the question to
improve it as much ...
You should never add the "Possible duplicate" note into a question yourself.
The note is placed there automatically by the system when the message is closed through regular means (users voting to close it).
If you see a question that is not closed, but you're certain that it is a duplicate, then feel free to vote to close it. However, this option is only ...
There are several different states for this situation:
The original question is still relevant:
If the original question is understandable, has high-quality answers, and the answers are still relevant and useful, then the new question should be closed as a duplicate. If there are any useful answers with new content on the new duplicate, then the questions ...
I think there are two cases.
The original question makes it clear that it's for a specific version. In this case, if you have a new question that related to another version of the OS, just ask it and make sure that you reference the old question. Tell us why the solutions there do not apply to the new version. However, it would be preferable to do this if ...
The blurb is basically good advice but the wording could be improved.
This isn't what bounties are for.
Don't be overly concerned about the dupe, yet. Think of it more in terms of "when" than "if".
The point of the bounty system:
Bounties are good for the author of the question when no good answers have been received.
While I try to be impartial here, one of the answers to the "duplicate" is mine. So keep this in mind.
This issue is not straightforward.
The older topic
requires matching based on name and file size
of all files in a given set (i.e. pairwise comparison)
The newer topic
requires matching of file contents only
requires the ability to set a reference file ...
Disclaimer: I was the OP mentioned.
Unless we're going to introduce the policy of closing different questions as duplicates, based on the fact that they may have a few same answers, I object to this. There are enough closing policies that it's hard to keep track of them as it is!
When one searches for a solution, one doesn't search answers ... he searches ...
This is a perfect candidate for a community-faq topic: Everything you need to know about NTFS hard links, symbolic links, and junction points.
Either wait for the topic to be part of the canonical questions and answers drive, or start your own community-faq-proposed topic, have a moderator make it community wiki and wait for answers to arrive. Maybe start a ...
Most questions closed as duplicates are...duplicates
Why are questions able to be marked as duplicate without some more in depth review?
To be closed as 'duplicate' a question must be reviewed by no less than 5 separate community members (or more rarely, a single moderator or user that's earned a gold badge in one of the question's tags). This process ...
For the record, here is the list of those mentioned sorted by the order of votes. Also included, the number of questions tagged about the AV program.
It reads like this:
antivirus program - questions asked with this tag/upvotes on question
ms-security-essentials - 84/140
avast - 25/57
avira - 2/46
avg-antivirus - 39/44
clamav - 1/23
None - 23
There are two reasons why such comments appear:
They voted to close as a duplicate - The system will then automatically add a comment on their behalf pointing out what other question they consider to be the master or canonical.
They want to see what others think - Either they're unsure of the duplicate or they don't have the voting rights and leave it there ...
The only option is to post a complaint on a per incident basis within meta super user.
That's one option. The other options are
If you have 3k+ rep, you can vote to reopen
Editing the question to make it clear why it's not a duplicate not only puts it into reopen queue, also bumps it up to the front page allowing for people to vote to reopen
You can flag ...
The various aspects of the question are well laid out and I completely agree with Ben N's answer. What I want to focus on is the relative "gravity" of the issues.
One set of issues relates to scope and fit, and the preferred style of handling this. That deserves careful consideration and discussion because it will be somewhat of a precedent.
The other is ...
In the context of versions, the tags should reflect the scope of the question and answers.
If the Q&A is specific to a version, it should be tagged to that specific version.
If the Q&A work for every version, you can safely tag it windows and avoid duplicates.
If the Q&A only works for some versions, you could tag it like windows-vista windows-7....