enter image description here


A recent change moved question stats (ask date, view count, and active date) from the sidebar to under the question title. Like others, you may find this distracting, because the information is only occasionally useful, yet its new position results in it being the second thing you read on every page.

This userscript runs on any SE site, and restores the question stats back to their prior position in the sidebar, removing them from just below the title.

This is intended for desktop users. The position change was probably made to make it easier for those with narrow screens to see the stats. Should work on any browser that supports userscripts and ES6, including Chrome and FF.

For compatibility with Roomba Forecaster and with any other older userscripts that depended on the old location of question stats in the sidebar, make sure this userscript runs before they do, so that the #qinfo table it creates can be found by the other userscripts.

GitHub repository

Direct install link

  • 2
    Userscripts are more convenient for people to install if served directly from a URL. Probably the easiest way to do that is to have the script in a GitHub repository. Doing so would allow users to automatically obtain updates to the script, when that's needed due to yet more changes by SE. A GitHub Gist would also work, but doesn't provide the ability to have people make PRs or post issues. Either way, that allows you to include a direct install link, which users can click to install. Personally, prefer to go to the actual file and review it first (e.g. then click the "raw" link on GitHub). – Makyen Jul 26 at 10:35
  • Ironically, one of the delays in updating Roomba Forecaster was making sure that it worked regardless of which order the scripts ran in :-). Version 2.2.0 of Roomba Forecaster has been released. It should work with any execution order. However, having Stack Sidebar Question Stats run prior to any other scripts that rely on the old structure of the Sidebar should help quite a bit. – Makyen Jul 26 at 16:03
  • 2
    Because this isn't hosted as a separate file anywhere, I created a GitHub Gist of it. The primary reason is so people can click on an install link. I'd much rather there be such a link available to somewhere hosted by you. I'll try to keep that Gist updated, but if you move this to somewhere from which people can click to install, I'll redirect installs to that location. – Makyen Jul 26 at 16:08
  • @BrockAdams I'm willing to go with whatever is most appropriate. My hope had been that CertainPerformance would move the code onto GitHub where it would be possible to submit PRs. When I created it, I'd really hoped/expected my Gist to just be a stopgap. Unfortunately, that hasn't ended up being the case. Thus, I'd used the suggested edits as, effectively, a PR. :-; If it's more appropriate for me to create an answer, I'm happy to do so. – Makyen Aug 30 at 16:32
  • @Makyen, the separate answer approach has been used several times here (full disclosure: I've used it often). But if CertainPerformance is willing to state that you are an approved custodian/editor of his script and this question, then you can keep making edits and I can clear my review alarms in a timely manner without stepping on "bad" suggested edits that are really okay. – Brock Adams Aug 30 at 16:40
  • Note: the link I provided above to install the Gist (3rd comment down from top) is, unfortunately, locked to version 1.2 of the Gist. For files in repositories, when viewing a branch, GitHub provides a "raw" link which is to the head of the branch. I assumed it was providing a similar link for the Gist, but it looks like the default is to provide a "raw" link locked to the version being displayed at the time. This is the version-agnostic link to install from the Gist. – Makyen Aug 30 at 19:57
  • I'll make a repository. I didn't think it'd be necessary for something this small, but it sounds like it's a better approach. Never really used Github before, but I'll learn – CertainPerformance Aug 30 at 20:13

You must log in to answer this question.

Browse other questions tagged .