Skip to main content

Timeline for Allow moderators to hide a revision

Current License: CC BY-SA 3.0

29 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/
Mar 7, 2017 at 22:38 history edited PolyGeo
edited tags
Feb 7, 2016 at 17:21 vote accept Gordon
Feb 7, 2016 at 17:20 history edited TarynStaff
edited tags
Feb 7, 2016 at 17:20 answer added TarynStaff timeline score: 48
Aug 9, 2014 at 14:34 vote accept Gordon
Feb 7, 2016 at 17:21
Apr 24, 2014 at 13:50 history edited CommunityBot
Migration of MSO links to MSE links
Jan 30, 2014 at 1:32 answer added Jeromy Anglim timeline score: 4
S Oct 30, 2013 at 16:15 history bounty ended Andrew BarberMod
S Oct 30, 2013 at 16:15 history notice removed Andrew BarberMod
S Oct 23, 2013 at 16:48 history bounty started Andrew BarberMod
S Oct 23, 2013 at 16:48 history notice added Andrew BarberMod Draw attention
Aug 13, 2013 at 6:08 answer added user50049 timeline score: 39
Jul 31, 2013 at 8:55 comment added Gordon Mod @DoubleAA a rough estimate based on the pings I found in the chat suggests three requests per month. That might not be much in quantity, but given the quality of the problem, I don't think we should base the necessity to handle them quickly on these numbers alone. If you'd accidentally put your credentials in a post, you'd want us to protect you, wouldn't you?
Jul 31, 2013 at 8:46 comment added Double AA Can someone provide an estimate for how often this happens (eg. once a week in the Trilogy, twice a day across SE, every hour on SO)?
Jul 31, 2013 at 8:31 history reopened GordonMod
Jul 31, 2013 at 8:06 history closed Cody Gray
Himanshu
Tobias Kienzler
Martijn Pieters
Rory
Duplicate of Ability for mods to hard-delete a question or revisions [duplicate]
Jul 31, 2013 at 6:55 comment added Gordon Mod @benisuǝqbackwards A "link to flag the revisions to Community managers, which would then hide the revisions until handled and also takes care of the pinging" as suggested in my question pretty much achieves that.
Jul 31, 2013 at 6:45 comment added Himanshu @CodyGray - Okay that means a Community team member was active at that time.
Jul 31, 2013 at 6:44 comment added ben is uǝq backwards This is a good idea; but it's open to abuse (I know none of you are going to abuse it but still...). It also doesn't destroy the revision. Would it make sense to have all of these actions reviewed by a member of the community team, who can then destroy the revision so the user's personal information is still protected and the moderators actions are double-checked? It removes the potential for abuse but still allows you to act more quickly than you can currently.
Jul 31, 2013 at 6:43 comment added Cody Gray @hims056 The way this works is a user or moderator makes an edit that removes the undesired content. Then they get the community team or a developer to hard-delete the original revision. So in that case, animuson made an edit, then a community team member hard-deleted the OP's original revision.
Jul 31, 2013 at 6:36 comment added Himanshu I thought it is already implemented. Now I am too curious how animuson could hide it. See the revision.
Jul 31, 2013 at 6:32 history edited GordonMod CC BY-SA 3.0
explained why the suggested dupe is different and added a new idea about a flag reason
Jul 31, 2013 at 6:00 review Close votes
Jul 31, 2013 at 8:06
Jul 30, 2013 at 23:23 comment added user206222 Perhaps two buttons are needed: "hide" to simply hide a revision, and "rollback and hide" to rollback to the last revision (only) and hide the proceeding revision.
Jul 30, 2013 at 23:15 comment added Andrew Barber Mod I love the idea of 'hiding' them.
Jul 30, 2013 at 22:47 history edited GordonMod CC BY-SA 3.0
moar spehling
Jul 30, 2013 at 22:37 history edited GordonMod CC BY-SA 3.0
zpehling and grammah bcoz boltwatch things its impotent
Jul 30, 2013 at 22:27 history asked GordonMod CC BY-SA 3.0