Tag Info

Hot answers tagged

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 ...


3

I've made a small updated fork, which is simpler. It adds only the timeline link. And it works today. And I will most likely maintain it (while I use any SEN site): // ==UserScript== // @name StackExchange Timeline Links // @namespace stackoverflow // @description Add a timeline link to current question in the Stack Exchange Network // ...


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.


3

Check out the enumerations page on the documentation.


2

It is something of a historical accident that this method returns markdown, however it has become too dangerous to change it. Consider it status-bydesign for 1.0 and 1.1.


2

This has been done. question_id is now found on every element in the returned set. Updated documentation. Presumably the last change before 1.0.


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.


2

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


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

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


1

It is more or less redundant. I'd have to dig back into source control to find exactly why, but I vaguely remember action and timeline_type diverging late in 1.0 beta. Expect that route to get some tweaks (more-so perhaps than the typical method) in the 2.0 time frame.


1

This should be fixed now. The underlying post timeline is getting shaken up a little bit, so this method way experience some outages or changes in the immediate future.


1

Yeah, that containing HTML at all is a bug. Badge descriptions at the time of 1.0 freeze were all plaintext. A fix for this will go out with the next API build, which should be tonight sometime.


1

Some changes to the site display of a user's timeline percolated up to the API interface. They've been decoupled, and things should be back to normal.


1

Voting data will never be exposed (as a stream anyway) with great accuracy, as its too easy to correlate it with user activity*. Easier streaming of site updates (questions, answers, comments, edits, etc.) is something I'm considering for the next version, though. *Provided some minimum amount of traffic to the site, anonymity is more or less ...



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