9

Here's a small and simpler updated fork. It adds only the timeline link: // ==UserScript== // @name Stack Exchange Timeline Link // @namespace stackoverflow // @description Add a 'timeline' link to Stack Exchange / Stack Overflow posts - based on http://stackapps.com/questions/2047/add-timeline-and-revisions-links/4238#4238 // @include ...


9

Good idea. There's a few minor niggles, though: Don't use unsafeWindow, this will break in Chrome and will not even work in Firefox+Greasemonkey if the effective @grant changes. Avoid leading * wildcards in @includes, if you can help it. This is a big performance hit. @match limits the wildcard scope and performs much better and reports the sites/...


5

This is a bug. The timeline path seems to have several problems. More on these below. The earlier date query returns the result you expect, but look at it in the document explorer: Notice that the entry is a comment and that it has an Owning post. Now if we look at the whole timeline (filtering out some user cruft), we see: Just two revision entries for ...


3

I'll use this answer to keep track of progress such as bugs and plans. That way it will be able to keep everyone up to date on the progress. Acknowledged Bugs Does not work on other browsers like Chrome (WIP) Future Plans Add support for even more question views.


2

That URL is malformed in a particular way that ASP.NET treats specially (as if it were an attack). /1.1/questions/51812/timeline?pagesize=100?page=2 should be /1.1/questions/51812/timeline?pagesize=100&page=2


2

Nope, this was a serialization bug. A fix has been deployed.


2

This was fixed in the latest deploy. The bug was basically selecting the wrong date to display (in this case, an associated post), and the right date for filtering and what not. Since not all badges are associated with a post, not all displayed dates were set and when they were set they were off by some (basically random) amount.


1

You shouldn't be making more than 4 requests in this case. fetch a page of /users/{ids}/timeline group the ids by type (question, answers, comments) since the max pagesize fo users/{ids}/timeline is 100, we know there are < 100 of each id* make 1 query each with the appropriate ids to /questions/{ids}, /answers/{ids}, and /comments/{ids} This is the ...


1

This was a fun one. Turned out there was a bug in cache for counts, that only affected this particular method. It has been fixed.


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