I believe cross-dupes not only are acceptable, but a small overlap is even useful:
If the scopes of the sites overlap, so should their content.
While a minor overlap does no harm at all, a gap between the sites would harm both.
For both sites being useful and complementary, provide an uninterrupted learning curve, the "travel" ...
If the answers there do not meet your needs, asking a new question is fine but it is on YOU to explain why the existing question does not meet your needs.
Include this information in your new question and it should be fine but make sure to give clear and accurate reasons why the other post was not what you wanted.
Yes, we can be hard on duplicates but they ...
The recent change to post notices does not change which posts are visible. It changes what information about their closure is visible. When you're logged in, you've probably seen text in post notices like:
(Viewable by the post author and users with the close/reopen votes privilege)
That text is referring to some of the information in the post notice ...
It has less to do with the age of the posts and more with the quality.
As you can see, the newer question has a couple of high quality answers, which go into a decent amount of detail around >, 1>, 1> and &> and what they each do and why you might want to use one over the other.
The older question doesn't have as high quality of answers, so ...
There is no ban for deleting a single post. In fact deleting your own question or answers when you realize they may not be helpful is encouraged. This will help to keep the site clear.
There is also no ban or other sanction in case you decide to delete your duplicate question but in general it may be better here to leave them as a signpost for other users ...
What I usually do is use the score:# option.
For example: search for broadcom drivers score:10, or even shorter, just broadcom score:10. Take a look at this:
score:10 means "show me questions with a score of 10 or more". This removes those low-score questions from the list, making it easier to spot the question you're looking for.
Of course, you don't ...
Personally I don't upvote answers to questions which are clearly duplicates ("clearly" = I can find an almost exact duplicate in the first three pages using the search function or in the first page using Google), because that encourages answering duplicate questions instead of closing them, which is the Right Thing(TM).
That being said if I catch an user ...
I just vote to close.
The site offers a duplicate search, some users use it, some don't. Sometimes if you notice a trend, you can do a search for a common duplicate and then just flag a bunch at once.
For example I do a search for "black screen" and "freeze" on occasion and always find some getting through. Just keep flagging them! The only time I ...
Asking here on meta is one way, asking in chat is another. But the best way to get your question reopened is to edit it with an explanation of why it isn't a duplicate. Comments are good but edits will put your post in a queue of potential reopen candidates.
Another good option would be casting a flag. Use flag -> in need of moderator attention and explain ...
If your answer is addressing the specifics of the current question and is sufficiently different, then yes, it may well be better to post it. Sometimes, you can post your answer addressing the specifics and vote to close as a dupe. Or, which I often do, vote to close and leave a comment along the lines of "Use the solution of the duplicate, just change foo ...
I can see situations where answering and closing would be the right option.
There are some processes that are pretty daunting to new users. Boot errors, graphics driver foul ups, random crashes. You can throw them at a 10,000 word generic answer —or even try to improve an answer— but they're left having to follow it. It's not always possible for every level ...
It's just a duplicate that went hot before anybody found the dupe. The audit system frowns on downvoting or closing posts it picked as examples of good posts, even if they are legitimate actions. It's dumb, but, it is what it is and what it is is difficult to improve.
I'd suggest that you always click the link to the post to verify you're shown the actual ...
A duplicate contributes to the master question's links on the site (and FAQ-ability), and it also acts as an automatic redirect page to the master question when a user comes in from a search engine.
So in other words, it's a sign post that points people in the right direction. I would just leave it, shrug.
For the record, questions are only duplicates when the questions are the same. Answer overlap is a fact of life, let it happen. People are going to search for their problem, not someone else's similar problem.
Absolutely. The age of a question is completely irrelevant when choosing duplicates. What we want is the best, most comprehensive and inclusive answer. If a question asked today has better answers than one asked four years ago, we should close the old one in favor of the new.
People often think that the age of the question should somehow be a factor when ...
Sorry, this is the norm.
We want the best answers for people - and good questions attract good answers.
So having a bad question redirect to a good one is much better than the other way round - and why edit the bad one to make it good when you have a good one?
It's pretty standard to do this as well.
As to the negatively on your record, I try not to see ...
If the question has a bad title, edit it
if a question's title is an obstacle to find the real content of it, I edit it into a more appropriate title. You can think of the following situations:
A question is more specific then needed, e.g.:
"How do I copy a file from command line in 14.04"
Copying files from cli is not Ubuntu version -...
Provided a question is a clear duplicate to an existing question.
What is ok
vote to close as duplicate. This will immediately direct the OP to the solutions posted there.
add an own answer to the previous duplicate if your solution did not yet exist there.
What is also ok
only if the previous question does not have any good answers:
write a brilliant ...
When that happens I will unleash my 42 special questions that I have in store but only for very special occasions such as this one.
Each of this questions will trigger sleeper ubuntu agents in the community that will also have 42 more questions each, which will also trigger other deep sleep agents with 42 more questions and so on...
Good you brought this topic to attention. It is true, we do not have a good canonical question/answer for data recovery but quite a lot of questions on that. So yes, we do need a canonical answer here.
So now here are my thoughts why we may have not done this yet, and what needs to be taken into account when we plan to:
Data recovery is a wide field where ...
Personally, I think that the best solution would be to develop a way of sharing questions across all sites where they're on topic. The rules against cross-posting were developed back in the days when there was very little overlap between the subject matter of different SE sites. However, things are very different today. The question you mention would be on ...
We encourage users to explain what they've tried, what didn't work.
In the case of something like your example:
CLOSE VOTERS: please don't close this as duplicate because it is not because A,B,C.
That is exactly the sort of thing that should be in the question. All they're
really doing is telling people what they've tried before. Or how their question ...
I regularly see the same question asked by the same user in both places. I think they believe that it increases the chance for a good answer as more eyes see it. It probably does. I can't blame them for trying.
In fact, in my particular area of limited expertise, there are several users that are frequent answerers at both places as well. Because of this, a ...
Yes, you're right that your question wasn't a duplicate of the linked question, because you already enabled the repositories that provide "ddeb" debug symbol packages (the -dbgsym packages), and both answers to the linked question were just about doing that. Fortunately, Seth has reopened your question.
Anyway, regarding the matter of moderators ...
Duplicates should be merged in whichever way requires the least effort to consolidate good answers between the two.
For example, If a newer dupe has one excellent answer, and the older dupe has a bunch of redundant info split between five answers, it's probably easier to close the older one (and copy the best bits to the newer one).
Speaking for myself, I ...
Mark as duplicate (if you have sufficient privileges) or flag it as such. A header with the appropriate message will direct users to the right duplicate with the most useful posts.
In my opinion this is not different from any other issue we had about a flood of similar/near identical questions when Ubuntu mobile/touch was presented.