61

Oh, hey, someone noticed! Indeed, you're correct. We've added a history event to both the edit history and the timeline to indicate when a question first appears on the Hot Network Questions list. This was made possible by the work Adam did recently to move where we house the HNQ list in our code. This will only indicate when a question appears - there's ...


40

Up until last week, moderators would have to contact the Community Managers to redact private information from a post, but thanks to Jarrod this is now been turned on for moderators to handle. By going to the post revision page, mods will now see a redact option: Choosing this, you'll be provided with the standard editing controls where you can remove ...


35

I like this idea because moderators are almost always the ones that spot this and bring it to our attention. In order for this to be implemented, we need to be able to soft delete (or hide) revisions. Currently, destroying a revision of a post means just that - hard deleting it. While I'd like to keep that functionality around for the next time someone asks ...


32

We no longer hard delete revisions. Instead, we now redact them. And currently, moderators have that ability too. So instead of contacting us if you for some reason accidentally posted sensitive information, please proceed by editing your post to have said information removed and replaced with dummy text/data/code that fulfills the same purpose — take care ...


27

This has been addressed and should be in the next build. We tried the exploding computer trick, but testing got expensive. After that, we decided to have these kinds of edits that occur within the grace period leave a revision behind, but with a comment ("Edit removed during grace period") indicating that the edit was a "grace-period reversion". The grace ...


27

SMITH: Doctor, it hurts when I do this. DALE: Don't do that.


25

I'm not sure why it's displayed in the order that it is, but I actually cast the second re-open vote on that question, so what you're seeing is in fact an artifact of the re-openers not being displayed in the order that they voted. I'm not entirely sure if that's by design, however there's no sort of privilege escalation at play here. Update This does ...


22

To clarify why I view this a bug, consider that the "grace period" for edits is already a compromise: unlike many wiki systems, Stack Exchange does not have any notion of "minor" edits, changes that don't fundamentally alter the meaning of a post. We encourage substantive edits, but of course mistakes do happen - so to prevent mile-long revision histories, ...


21

This was implemented earlier this week and is available to diamond moderators on each site. By going to the edit summary, you'll see this: And can edit out any inappropriate message that was left by the editor.


19

Yes, and it's available via the API, too, as a revision of type 52. It'll probably end up in SEDE as well (we should know for sure by Sunday morning); this will allow for some interesting data analysis too. (Too bad I have a holiday planned for next week ...) A GET request to https://api.stackexchange.com/2.2/posts/60613/revisions?site=aviation gives


16

When you edit an old revision, it'll be copied over the current revision and becomes the new version of the post. It is a shortcut to rollback+edit. I would have pointed you to How does editing work? but at the time of your question this particular information was not there yet; I've added it in.


16

I delete possibly more comments on a daily basis than most moderators, so I'm going to talk a bit about my experience. Interpersonal Skills has a very strict comment policy - though, we're merely codifying and enforcing Stack Exchange policy regarding comments. As such, comments are flagged and removed at a rate of about 1000 per month. There's (at least) ...


15

No, the the idea of providing that edit history is to maintain total transparency about what is being done with a post. There are limited cases where we may redact certain information that was posted inadvertently (e.g. highly-sensitive or personal information like a password), but you would need to 'flag' the post for moderator attention or use the '...


12

It appears we've hit an area here where CSS browser compatibility can still use some work. I checked five browsers, and got three different results: Safari and IE agree, Chrome and Opera agree, and Firefox stands all alone, also being the only one where it looks really totally broken. When using pre-wrap as Martijn Pieters suggests (and it's really the ...


12

Stack Exchange employees have, and always had, the power to make edits without leaving a trace in the revisions. This is useful for cases like posting private information by mistake (e.g.passwords) or, as in this case, some major trolling with extreme bad language. So the SE employee who appears as the editor made such a permanent edit without leaving a ...


12

Sorry about this - I over-encoded (we're trying to be as safe as possible everywhere) with some changes we're making on the road to .NET Core. This specific one has been reversed and all is right with the world again! We have some more major project changes for our migration being merged in this week...hopefully this sentence is your only awareness of them :...


11

This took an insane backfill to get the data in a proper state for display, but it's now done. For the vast majority of "closed as duplicate" questions, you can see the chosen originals in the revision list. There are a few very old closures that we couldn't figure out, but anything closed after 2009-05-20 11:52:52.627 should have something to display.


11

The issue with retag being different from edit is moot, as retag is gone. With edit, it is now enabled on deleted questions, unless they are self deletes, as this can open a window to abuse (self delete, edit and later undelete immediately). You can now also see revisions on your own deleted question, just like it is already possible with answers.


11

More easily, if the post hasn't been edited, copy the post id contained in the URL shown by clicking on "share" below the post (the first number, e.g. for this answer that is 273594) and go to the URL formed as below: meta.stackexchange.com/posts/273594/revisions Then click on "source". Otherwise, if the post has been edited, just click on the "edited [......


11

A picture says a thousand words... :P


11

Sure enough, there wasn't any proper validation on the notice types when bounties were started. There is now. Thanks for the report and I have refunded your bounties.


11

feature-requestdesigntimeline Currently for the hot questions, there is an entry added in the timeline. But due to the lengthy text the UI is looking inconsistency with the other row entries as below: Moving the "this question was selected for the hot network questions list." text under the comment section will be preferable UI. Could be the UI update ...


10

Yes, there is a way to do this. See the below picture for a guide on the rollback feature: In essence, this button will immediately revert to the edit that it is placed under.


10

Moderators should be able to edit these comments, just as they can edit comments. While history (for both of these!) right there in the UI would be better, for comments it's been declared good enough that the history is in the database (so SE can investigate complaints against mods doing this). If it's good enough for comments, which are more visible, then ...


10

No, neither moderators nor high-rep users have the ability to delete revisions. The dev team can, as long as there's a subsequent revision (they can't delete all the revisions for a given post) This comes up when users accidentally post their password or other confidential information. You can edit the post to remove it (creating a new revision), flag it ...


10

Don't know what exactly was in that question, but this happens when a moderator edits something out of the post and the previous revision gets burned (usually when it contains personal information). According to the timeline, the post was created by omg. Jeff must have removed and burned something from the question. I don't really care to investigate it any ...


10

Starting from the next build, instead of "suggested", the link text in the revision list will be "edit approved", if the revision originated from a suggested edit. rev 2014.7.29.1731, meta rev 2014.7.29.2401


10

Transparency is obviously a good thing. This feature request brings some extra transparency which is positive. There is a concern though, as Pëkka already mentioned: security risks. If a moderator removes some credentials, you don't want anyone to go search for that post on the cache of Google for example. Besides that, users that are not familiar with the ...


10

As others have surmised, there are lots of reasons why you might be able to "improve" a suggested edit without getting credit for it: You could've hit your limit for suggested edit reviews that day You could've somehow gotten review-banned after loading the review task but before submitting the edit The site could've logged you out or expired your token in ...


Only top voted, non community-wiki answers of a minimum length are eligible