I'm not sure what happened but up until recently the user/recent page seemed to get the most recent stuff by just refreshing. Now the first time the page loads, it gets a 302 redirect that adds in some params that lock in the date.

This might be the same issue as this post But that one is old enough that I'd think I would have spotted it well before now.

Whatever the case, the way it is now is just flat broken for anyone who wants to use tabbed browsing effectively.

  • It is most likely related to some tangential complaints about the timestamp of the recent envelope being inaccurate. The new update causes it to clear off any responses pretty much immediately after you have read them. I'm not sure how I feel about this.
    – Grace Note StaffMod
    Sep 21, 2010 at 16:43
  • It also causes Chrome's recent history conveniences to become less useful for SO. I dislike the change. Sep 21, 2010 at 19:21
  • BTW: end date accepts dates in the future so for 90 days at a stretch you can avoid this problem
    – BCS
    Sep 21, 2010 at 22:34

1 Answer 1


This has been reverted; sorry for the pain.


You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .