Skip to main content
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Source Link

I think there are several things you can do, and they should all be taken as parts of a whole: They should be implemented together for full effect.

  1. Extend "Vote to Close" voting limits for duplicates. In other words, don't rate limit voting to close duplicates.

    Effect: This will solve a common problem that these types of questions have, They've been asked beforeThey've been asked before. It will also allow the question to be closed, merged, and then editors can clean up the question (and we generally do).

  2. Create a flag reason called "Flag for editing"Create a flag reason called "Flag for editing". Add this to the existing flag reasons. I can't be everywhere; but I can guarantee if I saw posts that were flagged for editing I'd give those my attention (they should accumulate like other flags so that I can tell which ones need it most).

    Editors like editing questions. I happen to love trying to find clearer ways to help the asker ask his question. It's a fun and interesting challenge for me.

  3. Give out a badge for users that edit questions that were at negative score and then received 5 upvotes after their edit. This is only for the editor that changed the most percentage from the original post, and only the first editor to do so before it accumulated the votes (or items that make it work better).

  4. Incentivise finding duplicatesIncentivise finding duplicates.

  5. If a user has an excessive (3?) posts flagged 6 or more times as his post needing editing, he's rate limited in the next question he can ask. That's the built in time-delay system.

I think there are several things you can do, and they should all be taken as parts of a whole: They should be implemented together for full effect.

  1. Extend "Vote to Close" voting limits for duplicates. In other words, don't rate limit voting to close duplicates.

    Effect: This will solve a common problem that these types of questions have, They've been asked before. It will also allow the question to be closed, merged, and then editors can clean up the question (and we generally do).

  2. Create a flag reason called "Flag for editing". Add this to the existing flag reasons. I can't be everywhere; but I can guarantee if I saw posts that were flagged for editing I'd give those my attention (they should accumulate like other flags so that I can tell which ones need it most).

    Editors like editing questions. I happen to love trying to find clearer ways to help the asker ask his question. It's a fun and interesting challenge for me.

  3. Give out a badge for users that edit questions that were at negative score and then received 5 upvotes after their edit. This is only for the editor that changed the most percentage from the original post, and only the first editor to do so before it accumulated the votes (or items that make it work better).

  4. Incentivise finding duplicates.

  5. If a user has an excessive (3?) posts flagged 6 or more times as his post needing editing, he's rate limited in the next question he can ask. That's the built in time-delay system.

I think there are several things you can do, and they should all be taken as parts of a whole: They should be implemented together for full effect.

  1. Extend "Vote to Close" voting limits for duplicates. In other words, don't rate limit voting to close duplicates.

    Effect: This will solve a common problem that these types of questions have, They've been asked before. It will also allow the question to be closed, merged, and then editors can clean up the question (and we generally do).

  2. Create a flag reason called "Flag for editing". Add this to the existing flag reasons. I can't be everywhere; but I can guarantee if I saw posts that were flagged for editing I'd give those my attention (they should accumulate like other flags so that I can tell which ones need it most).

    Editors like editing questions. I happen to love trying to find clearer ways to help the asker ask his question. It's a fun and interesting challenge for me.

  3. Give out a badge for users that edit questions that were at negative score and then received 5 upvotes after their edit. This is only for the editor that changed the most percentage from the original post, and only the first editor to do so before it accumulated the votes (or items that make it work better).

  4. Incentivise finding duplicates.

  5. If a user has an excessive (3?) posts flagged 6 or more times as his post needing editing, he's rate limited in the next question he can ask. That's the built in time-delay system.

Fixup of bad MSO links to MSE links migration
Source Link
Fixup of bad MSO links to MSE links migration
Source Link

I think there are several things you can do, and they should all be taken as parts of a whole: They should be implemented together for full effect.

  1. Extend "Vote"Vote to Close"Close" voting limits for duplicates. In other words, don't rate limit voting to close duplicates.

    Effect: This will solve a common problem that these types of questions have, They've been asked before. It will also allow the question to be closed, merged, and then editors can clean up the question (and we generally do).

     
  2. Create a flag reason called "Flag"Flag for editing"editing". Add this to the existing flag reasons. I can't be everywhere; but I can guarantee if I saw posts that were flagged for editing I'd give those my attention (they should accumulate like other flags so that I can tell which ones need it most).  

    Editors like editing questions. I happen to love trying to find clearer ways to help the asker ask his question. It's a fun and interesting challenge for me.

     
  3. Give out a badge for users that edit questions that were at negative score and then received 5 upvotes after their edit. This is only for the editor that changed the most percentage from the original post, and only the first editor to do so before it accumulated the votes (or items that make it work better).

     
  4. Incentivise finding duplicates.

     
  5. If a user has an excessive (3?) posts flagged 6 or more times as his post needing editing, he's rate limited in the next question he can ask. That's the built in time-delay system.

     

I think there are several things you can do, and they should all be taken as parts of a whole: They should be implemented together for full effect.

  1. Extend "Vote to Close" voting limits for duplicates. In other words, don't rate limit voting to close duplicates.

    Effect: This will solve a common problem that these types of questions have, They've been asked before. It will also allow the question to be closed, merged, and then editors can clean up the question (and we generally do).

  2. Create a flag reason called "Flag for editing". Add this to the existing flag reasons. I can't be everywhere; but I can guarantee if I saw posts that were flagged for editing I'd give those my attention (they should accumulate like other flags so that I can tell which ones need it most).  

    Editors like editing questions. I happen to love trying to find clearer ways to help the asker ask his question. It's a fun and interesting challenge for me.

  3. Give out a badge for users that edit questions that were at negative score and then received 5 upvotes after their edit. This is only for the editor that changed the most percentage from the original post, and only the first editor to do so before it accumulated the votes (or items that make it work better).

  4. Incentivise finding duplicates.

  5. If a user has an excessive (3?) posts flagged 6 or more times as his post needing editing, he's rate limited in the next question he can ask. That's the built in time-delay system.

I think there are several things you can do, and they should all be taken as parts of a whole: They should be implemented together for full effect.

  1. Extend "Vote to Close" voting limits for duplicates. In other words, don't rate limit voting to close duplicates.

    Effect: This will solve a common problem that these types of questions have, They've been asked before. It will also allow the question to be closed, merged, and then editors can clean up the question (and we generally do).

     
  2. Create a flag reason called "Flag for editing". Add this to the existing flag reasons. I can't be everywhere; but I can guarantee if I saw posts that were flagged for editing I'd give those my attention (they should accumulate like other flags so that I can tell which ones need it most).

    Editors like editing questions. I happen to love trying to find clearer ways to help the asker ask his question. It's a fun and interesting challenge for me.

     
  3. Give out a badge for users that edit questions that were at negative score and then received 5 upvotes after their edit. This is only for the editor that changed the most percentage from the original post, and only the first editor to do so before it accumulated the votes (or items that make it work better).

     
  4. Incentivise finding duplicates.

     
  5. If a user has an excessive (3?) posts flagged 6 or more times as his post needing editing, he's rate limited in the next question he can ask. That's the built in time-delay system.

     
Migration of MSO links to MSE links
Source Link
Loading
Post Made Community Wiki by rds
george, you've been a user for HOW long and you still don't know how to format posts? sigh...
Source Link
Jeff Atwood
  • 311.4k
  • 107
  • 889
  • 1.3k
Loading
added link to related [feature-request]
Source Link
perbert
  • 17.2k
  • 4
  • 46
  • 96
Loading
Source Link
George Stocker
  • 84k
  • 31
  • 179
  • 378
Loading