Timeline for Incorrect audits
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 20, 2017 at 10:31 | history | edited | CommunityBot |
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
|
|
| Apr 24, 2014 at 13:41 | history | edited | CommunityBot |
Migration of MSO links to MSE links
|
|
| Feb 7, 2013 at 9:15 | vote | accept | Emil | ||
| Feb 6, 2013 at 13:31 | comment | added | user50049 | @BoltClock'saUnicorn I am an ape, actually | |
| Feb 6, 2013 at 13:30 | comment | added | BoltClock's a Unicorn Mod | No, you are monkey, and I am unicorn. | |
| Feb 6, 2013 at 13:26 | comment | added | user50049 | @benisuǝqbackwards I considered proposing that when I first learned how the system would work. As far as I know, this is the first case of this happening, if it becomes a bigger issue it's definitely something to consider. I'd rather not have more buttons and knobs in our tools, I'd rather it be automatic based on how much time we spend examining something expanded in the dashboard (if you could see the dash, that would make sense). | |
| Feb 6, 2013 at 12:52 | comment | added | ben is uǝq backwards | "So, in this case, I think I probably made a mistake. I could have validated the flags (I did fully agree with them) and left the answer after at least a minor edit to improve it a bit" I don't agree that you made a mistake deleting the answer; that does not mean that it should be an audit. Maybe a little check-box that you could unclick (less work) to stop something becoming an audit would stop the edge cases getting in there. | |
| Feb 6, 2013 at 12:29 | history | edited | user50049 | CC BY-SA 3.0 |
deleted 5 characters in body
|
| Feb 6, 2013 at 12:14 | history | edited | user50049 | CC BY-SA 3.0 |
added 169 characters in body
|
| Feb 6, 2013 at 12:00 | history | answered | user50049 | CC BY-SA 3.0 |