Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Post History
Some mitigation: Sometime in the last several months (sorry I missed updating here at the time), we added a flag type that is visible to people with the Curate ability: Change post status Th...
Answer
#1: Initial revision
by
Monica Cellio
·
2024-12-09T22:10:31Z (12 days ago)
Some mitigation: Sometime in the last several months (sorry I missed updating here at the time), we added a flag type that is visible to people with the [Curate ability](https://meta.codidact.com/abilities/flag_curate):  > Change post status > This post should be reopened/closed, locked/unlocked, or deleted/undeleted. Please elaborate in the details field below. Using this flag type increases the pool of people who can respond if a post should be reopened (or have other state changes). I admit that currently it is not a *large* increase -- we know abilities are too hard to earn and we need to figure that out -- but moderators can also make explicit ability grants where that's helpful, so at least there's an option to appoint more people to carry out these actions. A long time ago we sketched out a design for *ongoing* voting on closure, so instead of having close-reopen cycles on SE, people could counter-vote to say "no, keep it open" if a post was nominated for closure. This all depends on having a mechanism that even involves multiple people -- these are single-person actions right now -- and I think we (all, not just the team) need to think more about how we want this to really work before starting that project.