We are having an error with the flag as duplicate radio box. It never fills out, but just says 404. If one  of the developers could take a look at this, that would be great.
41764
This is maybe a duplicate like , but the error still appears.    When I try to click "mark as duplicate" a HTTP 404 error occur.  I'm using Firefox 16.0.2 with Firebug on Mac OS X 10.5.8
83521
iOS SEß 1.2.2.200  Since when did SE let you double flag?    There are two same flags in here.   Is it possible to be fixed?
54850
Today I saw a terrible thing in my profile     I'm a Deputy badge holder but my profile is only showing 10 helpful flags.  What is happened to my flags?  The flagging history also looks so confusing, missing many flags.
104229
I flagged something as spam, then was only 90% sure I'd done so, so I clicked the flag link again to check. It showed me this:    I had, of course, only raised the spam flag, not the offensive/abusive/hate flag, so the latter probably shouldn't be saying I did.    Ah, this may be a duplicate, I didn't search enough:        And if so, it's been around a while.
87255
So I understand that this has happened in the past: , but all of the &quot;duplicate&quot; posts are marked as  so here is a new bug report: On the , I am listed twice:  While that's fun and all, it isn't exactly right.
114028
I came across  today. In reading the answer and the comments it turns out that the issue was just a simple typo that the OP made. So that being the case I decided that this question probably needs to be closed since this will not be helpful to any future vistors. However, in looking at the flag reasons (I don't have the close ability yet), I don't see a flag that would be appropriate.   I know some of these options might still be influx because of the . However, until a different off-topic flag description is created, how should this be flagged? Or should this not be flagged at all and just allowed to live on or wait for a user with close votes to use a custom off-topic close option?
83906
Is the disputed flag handled any differently in the new triage review queue. I marked  as very low quality, after choosing unsalvageable and this was disputed. From what I have read, if a question is edited, this puts the flag in dispute, but this question was not edited. I have no complaint, I just want to understand what is going on, as the triage queue seems like a really good initiative, so I want to help as positively as I can.
23819
before :         after :        This is confusing. This is two different designs for the same thing. To sum the changes up:   Different banner on top of the post. Before: banner pushed as part of post contents and can be edited.   Worth to mention the "marked as duplicate by ..." message in the bottom is the same.  Suggested fix: simply run a script that within the same transaction Reopens all questions closed as duplicates before Feb 7th 2013 then closes them again as exact duplicates. If possible prevent this from bumping the question i.e. don't update the "last activity" time stamp.
33928
I just , which had been closed as  a duplicate of another.  I navigated away and went to visit the page later, it turns out, the Possible Duplicate banner wasn't removed automatically.        How come?
43003
I'm consistently receiving significant delays on Stack Overflow when opening the flag dialog on questions. Delays do not occur on any other StackExchange site I have checked. This started a couple days ago (as far as I can tell).  Delays occur not only when loading the initial screen, but also when loading the submenus. This is slightly confusing for a couple seconds (until you're used to it) since it appears as if the flag dialog has simply vanished.   What's going on here? I demand to know, otherwise somebody will be very upset.  Not me. I'm not going to get that upset over something like this.  But someone will.    Specs (though I know of several others who have this issue):  Windows 7 64-bit Chrome Version 30.0.1599.69m     Ping: 31ms Download: 6.88mbps   Upload: 1.07mbps
13542
On the  blog post, nearly all the images are broken. I assume this is because they are all hosted on stackoverflow.blog/wp-content/uploads/ rather than zgab33vy595fw5zq-zippykid.netdna-ssl.com/wp-content/uploads/, and they got destroyed in the removal of Blog Overflow. I looked around at a few other blog posts, and this post seems to be the only one having an issue.
21391
I went to flag something, and in the flag dialog I got the message  "Your last flag was declined - please review it before flagging this post!"    That's all well and good, but when I went to review my flags, the statement is not accurate.  My last 5 flags were all marked 'helpful'.  The 6th down the list is marked 'declined', but that wasn't my last flag.  The message should probably be modified to correspond to the actual condition that triggers it.  Perhaps it should say     One of your flags was recently declined - please review it before flagging this post!   I'm going to guess that this message is triggered if, of all the flags of mine that have been handled by a moderator, the one that was most recently handled was declined. This isn't necessarily the last flag that I raised (the one I raised most recently), as moderators might handle them in a different order than I raised them, and it's not necessarily the flag at the top of the list.  Thus, calling it my "last" flag seems like it could cause confusion.  Yes, I realize this is extremely minor.
34224
I hope someone can see this post because the same thing happens in the bugs tab on meta for me right now:     Edit:   works now.   still broken (as in screenshot).   Edit:  Go tag listing now working again.
67535
I am requesting for a new flag so that we can immediately flag questions in which people are asking for help on a problem from an ongoing contest, and if there is anything related to code or the algorithm in that question, it is deleted permanently from the view of others.  I am asking for this because I have seen a few questions, in which the OP was asking us to help fix their code on Stack Overflow. The Code they posted was from an ongoing contest on , and that would be considered cheating.  On codechef, we are told to not share anything from code, algorithm, or anything related to a problem from an ongoing contest, but since users are unable to ask their questions there, they come to Stack Overflow and ask it there.  Up till now, when I encounter questions like that, I flag them for moderator attention explaining the reason ( I don't have enough reputation to vote to close ).   I have not been a user on SO for long, but I have met a few questions like this already. This is one  . It's already deleted, but I think there should be a quick way to flag it so that it is brought to the notice of moderators quickly so that the code is not leaked. ( I don't want to increase the Work load on moderators, but something similar would be useful ).  So I request a new flag so that these questions can be flagged quickly to prevent the leaking of code and also make it easier, rather than having to type a good reason and wait for a moderator to accept it.  Please forgive me If this is a Duplicate as I could not find anything related to this on MSE yet.
64818
Previous posts                  As of today, the Moderator Flag Dashboard is officially graduated and the old version sent to the smelter's yard.  Based on stats from the past month, virtually all moderators were already on the new UI (thank you) so you hopefully won't notice any change.  That said, I would like to highlight the handful of improvements we made over the last month and a half based on your feedback:   A more responsive navigation bar at the top of moderator pages, improving the mobile experience. Similarly, , increasing room on the screen for the first question. . .  Not only do the headers look better, they now function better.  Now you scroll to and highlight the post/comment each time you click the link, not just the first time. .  Posts by the same user are grouped together and ordered newest first. .  We eliminated the VLQ (auto) side effect so now "Resolve all flags (auto)" doesn't do anything surprising.  If you still want to leave a comment or decline, you can do so with the buttons next to the individual flags.   Bugs and Feature Requests  Since this project is officially launched, all bugs and feature requests should be done in the form of questions tagged  on MSE, not answers on this post.  Feel free to post an answer here if you have specific concerns about the release process.
9082
It looks as if the 10k-tools flagged post list is b0rken.  Next to the review link in the toolbar there is a flag counter showing there are 10 flags to be reviewed:    Clicking on that flag counter leads to an empty page:        The moment I visit that page (through clicking on the flags counter, or by going to the review queue first then clicking on Tools, selecting the flags tab if not already selected), the flags counter disappears from the toolbar:    but after a while (half an hour, an hour?) the flag count re-appears in the toolbar.  Either the counter is wrong (presumably taken from a Redis cache somewhere) or the 10k flag review page is falling over every time someone tries to load it.  This at first appeared to happen only on Meta, on Stack Overflow the flags page has plenty to review. However, there are now  on Stack Overflow.
72101
Few arguments against it:   Pressing the flag button doesn't mean actually submitting it (as in every test/form). There might be an unknown duplicate, if you assume it's the first post (as you were told) it might be worthy to flag it. You might want to look if someone else thought it was duplicate by "making half way" to flagging it.   Why pressing the flag button makes you fail an audit? I think it shouldn't.  Edit:  The implementation difficulty (fake flagging UI) and the tips about how avoid failing (and reviewing!) by skipping the answer adds some insight, but still doesn't answer the question why it's not a valid review.    Moreover, I would like to add one more,  describes a reviewer that failed an audit while trying to flag a question as off topic. The question was clearly off topic, and still after 1300 views no one flagged it.