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 |
Indicates that a feature request has been implemented, a bug has been fixed, or another type of request has been processed.
4
votes
Accepted
Why is my quota constantly decreasing?
I believe this was related to some other throttle/quota bugs that have been recently fixed.
Basically, some networking assumptions were incorrect, and a lot of apps ended up appearing to be coming fro …
7
votes
Accepted
Key Limit is 10k or 100k?
Its 10k now, the way it was intended. Anyone with an active lease will stick to 100k until the day ends, or an update is deployed.
3
votes
Accepted
API documentation pages match some site names incorrectly
The console JS was doing fuzzy matching on ?site; but that's not really correct, as you demonstrated.
With the latest deploy it does an exact match if possible.
2
votes
Accepted
"Try it" facility suffers a double-encoding bug
This was fixed in the latest deploy.
3
votes
Accepted
Google’s OAuth redirect broken
This was fixed in the latest deploy.
2
votes
Accepted
Trying to get the Total results count crashes the /notifications path
This was fixed in the latest deploy.
Sorry about the wait, a fix was actually staged a few days ago but deploying it was delayed by our yearly company get together.
2
votes
Accepted
API calls that return select post bodies throw JSON errors
This was fixed in the latest deploy.
Root cause: I had let a copy of our JSON serializer (currently ServiceStack.Text) get out of date.
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
Accepted
Most of the url are missing the protocol
There was some monkeying around on the backend with URI generation, it's settled down now and this issue was resolved.
4
votes
Stack Exchange API is returning boolean(false) For 'is_answered' On Question With Accepted A...
Tricky.
This was a consequence of the API misinterpreting a normalized field used elsewhere in the system to indicate whether or not a post has upvoted answers.
Everywhere else, "is answered" is tru …
2
votes
Accepted
Stack Exchange API is returning non-existant/incorrect notices for questions
The bug here is that deleted notices were still being returned.
This was fixed in the last deploy.
1
vote
Accepted
/user/{id}/notifications API call
You can synthesize most/all of this call currently (new answers, changes in user rep, and comments directed at user are all accessible in v1.0) however it does take multiple calls.
We'll revisit this …
2
votes
Accepted
Stack Exchange API is not returning the close vote counts for questions
This was fixed in the latest deploy.
4
votes
Accepted
The API has stopped allowing CORS requests
This was fixed in the latest deploy.
3
votes
Accepted
Can we have maximum length of string in API help pages?
Alright, here's what we're going to try.
First off, we're not giving hard guarantees as to the maximum length of strings returned. Such a guarantee could create a situation where we might have to re …