Return to Question

Here is the question, that I was reviewing:

10 GB of RAM unaccounted for by top

It appeared as a new one, so I flagged it as a duplicate of How to interpret output from Linux 'top' command? (actually there are hundreds of the same "why my free command displays wrong memory" questions out there).

Then got this:

 STOP! Look and Listen.

 This was an audit, designed to see if you were paying attention.
 You didn't pass. Your review was inappropriate.
 This was a high quality post and you should have considered leaving it
 as-is or even upvoting.  

You know, I'm getting a feeling I'm the only one doing reviews for several weeks, since the "unreviewed" posts count only goes down when I'm doing it. Getting a test failure on such troll questions doesn't help my motivation in doing reviews at all.

---

I might just have a simple technical solution, that will once & for all eliminate this problem:

1. When flagging question as a duplicate, we already got "Similar questions frequently linked or suggested as originals" search field.
2. Exclude questions that have possible duplicates from the "review audit" questions pool.
3. Problem solved!

I'll explain a bit:

Look at the top rated questions, choose a random one, press "flag -> Duplicate" and check whether it has any suggested duplicates. If it doesn't, than it's a good test question. Here is an example of a good test question.

But if it does have a long list of possible duplicates like this one - exclude it from the pool, so it never shows as a test question.

I'm not saying this is anywhere near important, but it would be nice if this is implemented someday.

Here is the question, that I was reviewing:

10 GB of RAM unaccounted for by top

It appeared as a new one, so I flagged it as a duplicate of How to interpret output from Linux 'top' command? (actually there are hundreds of the same "why my free command displays wrong memory" questions out there).

Then got this:

 STOP! Look and Listen.

 This was an audit, designed to see if you were paying attention.
 You didn't pass. Your review was inappropriate.
 This was a high quality post and you should have considered leaving it
 as-is or even upvoting.  

You know, I'm getting a feeling I'm the only one doing reviews for several weeks, since the "unreviewed" posts count only goes down when I'm doing it. Getting a test failure on such troll questions doesn't help my motivation in doing reviews at all.

---

I might just have a simple technical solution, that will once & for all eliminate this problem:

1. When flagging question as a duplicate, we already got "Similar questions frequently linked or suggested as originals" search field.
2. Exclude questions that have possible duplicates from the "review audit" questions pool.
3. Problem solved!

I'll explain a bit:

Look at the top rated questions, choose a random one, press "flag -> Duplicate" and check whether it has any suggested duplicates. If it doesn't, than it's a good test question. Here is an example of a good test question.

But if it does have a long list of possible duplicates like this one - exclude it from the pool, so it never shows as a test question.

I'm not saying this is anywhere near important, but it would be nice if this is implemented someday.

Here is the question, that I was reviewing:

10 GB of RAM unaccounted for by top

It appeared as a new one, so I flagged it as a duplicate of How to interpret output from Linux 'top' command? (actually there are hundreds of the same "why my free command displays wrong memory" questions out there).

Then got this:

 STOP! Look and Listen.

 This was an audit, designed to see if you were paying attention.
 You didn't pass. Your review was inappropriate.
 This was a high quality post and you should have considered leaving it
 as-is or even upvoting.  

You know, I'm getting a feeling I'm the only one doing reviews for several weeks, since the "unreviewed" posts count only goes down when I'm doing it. Getting a test failure on such troll questions doesn't help my motivation in doing reviews at all.

---

And here is a simple technical solution, that will once & for all eliminate the problem:

1. When flagging question as a duplicate, we already got "Similar questions frequently linked or suggested as originals" search field.
2. Exclude questions that have possible duplicates from the "review audit" questions pool.
3. Problem solved!

I'll explain a bit:

Look at the top rated questions, choose a random one, press "flag -> Duplicate" and check whether it has any suggested duplicates. If it doesn't, than it's a good test question. Here is example of a good test question.

But if it does have a long list of possible duplicates like this one - exclude it from the pool, so it never shows as a test question.

I'm not saying this is anywhere near important, but it would be nice if this is implemented someday.

Here is the question, that I was reviewing:

10 GB of RAM unaccounted for by top

It appeared as a new one, so I flagged it as a duplicate of How to interpret output from Linux 'top' command? (actually there are hundreds of the same "why my free command displays wrong memory" questions out there).

Then got this:

 STOP! Look and Listen.

 This was an audit, designed to see if you were paying attention.
 You didn't pass. Your review was inappropriate.
 This was a high quality post and you should have considered leaving it
 as-is or even upvoting.  

You know, I'm getting a feeling I'm the only one doing reviews for several weeks, since the "unreviewed" posts count only goes down when I'm doing it. Getting a test failure on such troll questions doesn't help my motivation in doing reviews at all.

---

I might just have a simple technical solution, that will once & for all eliminate this problem:

1. When flagging question as a duplicate, we already got "Similar questions frequently linked or suggested as originals" search field.
2. Exclude questions that have possible duplicates from the "review audit" questions pool.
3. Problem solved!

I'll explain a bit:

Look at the top rated questions, choose a random one, press "flag -> Duplicate" and check whether it has any suggested duplicates. If it doesn't, than it's a good test question. Here is an example of a good test question.

But if it does have a long list of possible duplicates like this one - exclude it from the pool, so it never shows as a test question.

I'm not saying this is anywhere near important, but it would be nice if this is implemented someday.