173

I am happy to announce that a new and improved post timeline is now available to all users. It can be accessed by clicking the clock icon underneath the voting and favorite buttons that are located to the left of a question or answer. Clicking on the button will bring you to the timeline page for the given question or answer. This page shows everything ...


28

Protecting does not bump posts, so my protection of the question is not what caused it to be bumped. What actually happened here is that there was a spam answer that contained an NSFW image. Some time after it was deleted, Yaakov redacted that image from the post. Redaction does have a flaw, in that it only modifies the Markdown of a given post's revision, ...


24

The goal here isn't to make closing a secret process of some sort. It's often important to know what all has happened to a post, and why - so the revision history and timeline seek to provide this. Removing the names (and other details) from the default question view aims to preserve the bare minimum amount of information needed (the question cannot be ...


23

There are no permission issues with the timeline Thanks for notifying us of that... imaginary... issue. It's now fixed.


23

Redacted some porn Creates a small kerfuffle Answer too complex


22

Update: it should, but not to the ones that are currently being worked on As discussed below, it's rather more useful to see links to completed review tasks than those currently in flight. Also doesn't threaten to skew reviews so badly. So that's how we'll do it now: you'll see review tasks linked in the timeline once they're not currently live (completed or ...


21

This has been fixed! This took a while to triage because it touched a ton of different functions I wasn't used to poking around in, including the post history and post history revision generation. The Bug The source of the problem was a function that checked if the post history entry had any content changes. This is a function that effectively hasn't been ...


20

The users voted to migrate the question, but it was blocked by the system because the sole tag on the question, academic-writing, doesn't exist on the target site. When normal users vote to migrate a question, the question must use at least one tag that exists on the destination site, or else it will be blocked by the system in the same manner as if the post ...


17

The public timeline for all questions and answers is now available for all users. More details are available here.


17

Yes and no. As you can see from the timeline of this question, I was able to remove this very question from the Hot Network Questions (for science), even though 1) it wasn't hot at the moment 2) Meta Stack Exchange does not even have Hot Network Questions. The option to remove this question from HNQ was not shown in the mod menu, but it's rather easy to mock ...


16

So you found out my evil scheme of testing who uses that timeline uh? You foiled my plan once again Batman, but the next time it won't be so simple! Fix going out now. rev 2014.1.15.1851 on meta and rev 2014.1.15.1301 elsewhere


16

This bug seems to be much wider in scope, affecting actual site functionality, and not only display. Not only closing events are affected, but other events (locking, deleting, etc.) are also affected. See the below screenshot of a question's revision history: When actions by multiple people take place, the "edit" is attributed to the Community ...


14

Community bump attribution has now been corrected, as part of the recent upgrade for post timelines.


14

The underlying issue here has (hopefully) been fixed. Extra post history entries have been removed. The cause was a race condition on the hot network questions global cache: We cache Hot Network Questions (HNQ) across the entire network. The cache expires every 15 minutes. Every pageload (on every site) that shows HNQ hits this cache. As soon as the cache ...


14

They were not being reviewed as first posts. They were being reviewed as audits. Certain posts are eligible to be automatically selected as "known good" tests that users in those queues need to pass to prove they are paying attention. You can tell that a review was an audit by clicking through to it and looking at its completion: If it were a normal review,...


13

Because the review task was still ongoing when the question got either closed or reopened. Now that the action is already completed, there is no point in continuing the review process for it - so the task gets invalidated to prevent further reviews. Review tasks are only ever marked as completed when the final review is what causes the action to actually ...


12

Yes: please change this. The lack of this information gets really annoying when there are nontrivial changes in the accepted answer. If you want an example of a question with such changes, this one is a good one. In that specific case, the OP originally accepted my answer, and then some three years later changed the accepted answer to some other one, giving ...


12

Your sequence of events was correct thus far. The moderator did undelete the post manually (no idea why). However, there is an automated process that silently wipes out all answers on a deleted question. This process essentially just marks every answer as deleted, to make sure they all are, and runs every couple of hours (?). So when the moderator undeleted ...


12

The CC BY-SA license only covers content. Tags are (apparently) considered metadata. In the original implementation, they triggered a license change, but after the bug report, they no longer do (and I agree with that, FWIW). Comments are licensed under various CC BY-SA licenses, depending on when they were posted. At least SEDE and the API can tell you the ...


12

The point in keeping them is to see how often posts are being picked out as review audits and whether or not people are passing or failing the audits. Let's say someone complains that the audit is unfair. We can point to all the people who passed the audit, or we can point to all the other people who failed it to have some evidence as to whether it's fair or ...


11

With the release of the new timeline, the closed and reopened events will now display the users who voted to close/reopen the question along with the final reason (for closures). Totally random example here


11

This was caused by a race condition. Two users happened to cast a sixth spam flag on the post at exactly the same time, which caused the system to process all the resulting actions twice for the post because neither process knew anything about the other process already running.


11

A change went out that mistakenly prevented the Community user from being fetched from the DB. Since we assign flags and (occasionally) votes to the Community user in various cases (e.g. when a real user is deleted)... that causes a bit of a problem. :) The fix is out in production. Thanks for the report!


11

A diamond will be attached to everything you say and have said in the past, including questions, answers and comments. Everything you will do will be seen under a different light. How do you feel about that? When a user runs in a moderator election, that's what's asked of them. And I think that's how it should stay. It's an easy to explain rule: the diamond ...


10

The "view vote count" privileges is less about restricting access to the specific vote counts and more about limiting load on the servers. From Jeff's answer on Show Total Votes (or Up/Down Votes) The total vote count (score) is denormalized, but the individual up/down vote counts are not. So to display it on every post would incur 2 vote table ...


10

The issue has been fixed. Timelines are back.


9

Links to all completed reviews of a post as well as a bunch of other handy information can now be accessed through the timeline view. Historical Information: In case someone reading this doesn’t know what the timeline view is: It’s one of the hidden (experimental) features of all Stack Exchange sites. More detailed information about it can be found here. ...


9

Jeremy Banks wins: that hack was overzealously replacing commas everywhere, even inside scripts. It has been replaced with, hum, a more proper hack.


9

This remains fairly trivial compared to the other requests for breaking out close reasons, as the information is already displayed in the timeline for moderators. In light of that, I would recommend one small tweak to the proposal: Display all non-pending close and reopen votes in the timeline. ...where non-pending just means they've either already taken ...


9

While your suggestion seems reasonable, one problem is that edit summaries aren't editable by normal users. That could make it too easy for a bad actor to drop in spam, or links to porn, or other undesirable content that would be difficult to get rid of without Moderator intervention. I think a case could be made for links that stay within the Stack ...


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