background April 8, 2014

Changes and guidelines for the Protected Question status

Protected status is an often-overlooked feature of Stack Exchange. It’s based loosely on Wikipedia’s semi-protection, and like that tool is meant to be a reaction to persistent abuse from anonymous or unproven participants: when a page attracts a lot of noise or vandalism from outside the community, Protecting it reduces the amount of clean-up needed…
Avatar for Josh Heyer
Community Manager (former)

Protected status is an often-overlooked feature of Stack Exchange. It’s based loosely on Wikipedia’s semi-protection, and like that tool is meant to be a reaction to persistent abuse from anonymous or unproven participants: when a page attracts a lot of noise or vandalism from outside the community, Protecting it reduces the amount of clean-up needed later on.

Protected questions are not answerable by folks who haven’t earned at least 10 reputation from activity on the site where the question resides. This effectively means you need to have posted an answer somewhere else that’s attracted an up-vote or a question that’s earned two.

Originally, this functionality was limited to moderators, but during the past several years we’ve made a few changes to encourage more productive use:

  • Privileged users can protect and unprotect any question over a day old. Previous unprotect restrictions lifted as of today.

  • The system (in the guise of the Community user) will automatically protect questions that’ve had either

    1. 3 answers from new users deleted – this handles questions that tend to attract large amounts of spam over time.

    2. 5* answers from new users scoring <= 0 posted in the past 24 hours – this handles questions that are somewhat topical, and are attracting large numbers of “participants” who aren’t actually contributing anything useful. This is also new as of today.

*This value can be higher or lower on sites that have demonstrated “special” patterns of new-user interaction.

Guidelines for Protecting questions:¶

  • Do protect questions that are attracting a lot of non-answers or very poor answers (spam, etc.) from new users.

  • Don’t protect questions just because they’re linked to on a high-traffic news site like Reddit or Ars Technica. While there’s certainly some correlation between sudden spikes in popularity and associated non-answers, not all popular questions suffer from this.

  • Do unprotect questions that aren’t currently attracting a lot of attention and don’t have a long history of unproductive answers.

Judicious use of this feature is critical to allowing these sites to handle large amounts of external attention, but over-using it breaks the system: Stack Exchange sites depend on a constant influx of new blood, both to answer new questions and provide updated information on old ones. When in doubt, err on the side of letting new users prove themselves before locking them out.

Podcast logo The Stack Overflow Podcast is a weekly conversation about working in software development, learning to code, and the art and culture of computer programming.

Related

newsletter July 6, 2020

The Overflow #28: We heard you like lists

July 2020 Welcome to ISSUE #28 of the Overflow! This newsletter is by developers, for developers, written and curated by the Stack Overflow team and Cassidy Williams at Netlify. In the US, we’re celebrating our Independance Day, and hopefully reflecting on what freedom means and helping everyone share in that freedom. This week, we’re pondering…
newsletter September 4, 2020

The Overflow #37: Bloatware, memory hog, or monolith

September 2020 Welcome to ISSUE #37 of the Overflow! This newsletter is by developers, for developers, written and curated by the Stack Overflow team and Cassidy Williams at Netlify. Thrill to the veteran Stack Overflow engineer who walks like a noob! Gasp at the 2000-year-old temperature reading! Marvel at the GitHub README that writes itself!…