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 ...
I propose that the list be modified to something similar to what my ReduceClutter userscript already implements, and it is clearer which link was removed/added, and the new sort order (if it was re-ordered):
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 ...
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 ...
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 ...
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.
This does ...
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.
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
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 '...
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) ...
It is not yet added to the revision history but my earlier feature request to add this data to SEDE has been status-completed.
So until this gets added to the revision history you can now run this query
select pn.body as [Custom Comment]
, pt.Name as [Notice Type]
, pt.Body as [Reason]
This is fixed.
When working on review queues, I switched from using fixed width tables to flexbox for rendering the side-by-side HTML diff, and apparently <table> elements are just as stubborn about <pre> element width as flexbox, if not more so. Posts with wide enough code blocks caused the posts to explode outside of their containers.
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:
Then click on "source".
Otherwise, if the post has been edited, just click on the "edited [......
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 ...
Redactions are possible. The UI is a pain so discussing a workflow that works with your moderators is a great idea.
This is no different from any other personally identifying information - as if you'd posted your private key elsewhere or password in my opinion.
The latter is probably unlikely to happen, especially as something unique to a few sites. While ...
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 :...
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 ...
I didn't search other sites yet, but this post on Stack Overflow seems a winner to me. It has a whopping 753 revisions!
You can run this query on SEDE to get the results:
select PostId [Post Link]
where posthistorytypeid in (4,5,6,7,8,9,24)
having count(*) > 100
by count(*) desc
If you don'...
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 ...
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 ...
They are legacies of a long history of how we store tag data. Yesterday I completed our migration, but the migrate script did not quite allow for some broken-but-just-about-working data. In this case (you'll need to read the blog for this to make sense) the old data was:
Note the two spaces. Unfortunately, this got migrated to
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
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 ...
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 ...
The question was migrated from Stack Overflow. The complete revision history of migrated questions pre-migration isn't visible on the new site, and the revision history there only shows the most recent pre-migration revision but with the original timestamp. (see e.g. Does a migration remove edits from the edit history?)
You can see the full revision history ...