Search Results
Search type | Search syntax |
---|---|
Tags | [tag] |
Exact | "words here" |
Author |
user:1234 user:me (yours) |
Score |
score:3 (3+) score:0 (none) |
Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
Views | views:250 |
Code | code:"if (foo != bar)" |
Sections |
title:apples body:"apples oranges" |
URL | url:"*.example.com" |
Saves | in:saves |
Status |
closed:yes duplicate:no migrated:no wiki:no |
Types |
is:question is:answer |
Exclude |
-[tag] -apples |
For more details on advanced search visit our help page |
Tools that help with the post timeline feature, or issues with the API handling of /timeline routes.
2
votes
Accepted
/users/{ids}/timeline creation_date missing or incorrect
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 …
1
vote
Include Full Post Details In /users/{id}/timeline
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 …
2
votes
Accepted
Guid inconsistency in 2.0?
Nope, this was a serialization bug.
A fix has been deployed.
1
vote
Accepted
The /users/{id}/timeline route is reporting incorrect totals
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.
1
vote
Accepted
Error occurs when retrieving timeline for this question
/1.1/questions/51812/timeline?pagesize=100?page=2
should be
/1.1/questions/51812/timeline?pagesize=100&page=2 …
1
vote
Accepted
Timeline results contain redundant information?
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 …
3
votes
Accepted
Comments in user timeline are returning Markdown
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.
1
vote
Accepted
/user/{id}/timeline results leaking template used for badge information
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
vote
Accepted
Something's changed about user timelines
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. …
2
votes
Complete question timeline including votes
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, …
2
votes
Accepted
In the timeline the ability to know what events belong to what question
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.
1
vote
Accepted
The /questions/{id}/timeline route isn't working.
The underlying post timeline is getting shaken up a little bit, so this method way experience some outages or changes in the immediate future. …