Tag Info

Hot answers tagged

11

It could be a proxy between you and the API that is mangling the headers that are being sent and making the request without compression. This is one downside to mandatory compression. It might be nice if there was an https endpoint that could be hit to test these types of issues or even to fall back to. If the point of mandatory compression is to save ...


7

This is status-bydesign. The site being closed beta prevents people from participating so as to prove that the committers are actually, well, committed. Being able to read data out doesn't allow participation, so we figured why not allow it.


6

Now, I can confirm that changing my IP Address reset rate-limit to 10000 back. So, 10k limit is per IP Address, not globally.


6

Oy, that was an annoying one. Subtle, as the bug only happened when you're not logged in but would be automatically logged in when you visit stackexchange.com. The actual root cause was just over-encoding a url.


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


4

I think this is not specific to Stack Apps, All the reputation graph on Trilogy site don't show bonus points. For your case, 100 is from Account Associations, 4000 is from Api Evangelist badge bonus point. But I hope they could add those bonus info to reputation-graph as well.


4

Anything that supports a sort of activity can do this already. ?sort=activity&min={start-date}&max={end-date} Where start-date and end-date are unix timestamps. Update /questions and /questions/unanswered now honor min, max, and order. sort | min and max limit -------------------------------- active | last_activity_date newest | ...


4

Search intitle is now case insensitive.


4

There is a pretty good chance the Jon has hit the cap today. So he only got rep for the accept. The data is real time, so it is actually cached less than the website.


4

Note that Meta Stack Overflow is, and has always been, Meta Stack Overflow. not Stack Overflow Meta. Thus, these members of the trilogy inherit that naming choice.


4

No, this is expected behavior, Meta Stack Overflow is indeed a special case - see the original Per-Site Metas announcement, specifically the last paragraph: For now we are leaving meta.stackoverflow.com grandfathered in, as-is, with no changes; it’s still a standalone community with a standalone reputation system. We think Stack Overflow is ...


4

These typos were fixed in the latest build.


4

This will be fixed in the next build.


4

That is the 2.1 documentation, it's just the title (and perhaps the first sentence) that hasn't been updated. All of the routes added in 2.1 are there, so you don't have to worry that it's missing anything important.


4

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 true if either of the following are met: The question has an accepted answer The question has an answer with a score > 0 The API wasn't doing the "or" check. ...


3

I think www.stackapps.com should be redirected to stackapps.com, currently can see the same page but cookies validation looks failing


3

This will be ready on the next deployment of the API.


3

There are a great many fields on objects returned by the API that will be omitted if they are not set. The user fields you mentioned. locked_date, bounty_date, etc. on questions and answers a whole slew of user_timeline and post_timeline fields depending on the *_type of each ... and many more. We do this because omitting a field clearly indicates that ...


3

Yeah, just displaying blank string will be great. And also same for accept_rate age location website_url too (may be there is even some more) Note: Personally, I don't have any problem with existence of those field or not though


3

Adding max=-10 will only show score with -10 or lower questions http://api.stackoverflow.com/0.8/questions?sort=votes&order=asc&max=-10&type=jsontext


3

I see that api/stats is a little ahead of the question count: api: 710,258 site (logged in): 710,250 site: (not logged in): 703,405 This makes sense to me, none of those counts is completely live, I assume they are cached and regenerated only every so often (every 10 minutes?), to reduce server load. If the api and the site front page are not generated at ...


3

The question counts on the site are cached. They don't update realtime, so they will always be behind live numbers


3

Take a look at the answers parameter. Docs


3

Question titles aren't markdown, they're plain text. Accordingly, if you're going to display them in HTML you shouldn't display them "raw".


3

Question and answer data is almost instantaneous. I regularly see Questions with soapi-notify that are 7 seconds old. Answers take a few more seconds. Votes and acceptance sometimes take 30 seconds to a minute to register. Hard to be exact unless I am polling at a rate that may draw unwanted attention. So yeah, there is some latency but nothing more than ...


3

Obviously this would best be answered by the one(s) in charge of the API design, but here is my analysis: The two reputation datasets are shaped quite differently indeed and this does matter in various ways - as such I expect this to be more or less status-bydesign: Dataset shape The reputation audit is composed of individual reputation change events at ...


3

This has been fixed.


3

It has been more than 12 hours since I checked http://stackauth.com/1.0/sites, it is still returning a 404. Does anyone have an idea when http://stackauth.com/1.0/sites will be available?


3

Sorry about that, I had completely forgot I disabled Gzip compression in Firefox due to a misbehaving site a few months ago. This does explain why some JSON preview apps show garbage instead of actual JSON: They don't handle Gzip compression.



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