Tag Info

Hot answers tagged

5

I mean, the value's not wrong, just perhaps not useful? The QPM is taken over the entire lifetime of the site, so 10005086 / 3644369.9112 = 2.745354133577943, where 3644369.9112 is ((Date.now() / 1000) - site.launch_date) / 60 I'm not sure if there'd be a better default timespan though—it's probably better to just pull the question count for the period ...


5

Yes, that bug is annoying, especially since specifying a todate that's before the fromdate returns a valid result set, EG: { "items": [], "has_more": false, "quota_max": 10000, "quota_remaining": 9995 } -- rather than an error. Having the dates be equal is theoretically possible. Having negative time is impossible (in this context). However, ...


3

Confirmed the bug on a post that accrues comments much slower than a typical Stack Overflow question does. Currently, the OP's filter returns "comment_count": 1 on that post. There are no comments. I believe this is a side-effect/bug/quirk with how the API appears to be counting the comments. ¿Perhaps it is counting Ids in the comment table and not ...


3

This is a bug. I've tagged your question accordingly. total, in the wrapper object, should always be the length of the items array, after concatenating all pages of results. When I run /2.2/notifications?pagesize=100&filter=!*L6X1NqVdlFobvlv, I get 4 pages of results, currently totaling 382 items: total remains fixed at 77. This is clearly a bug, ...


3

It sounds like you've either got a bug which is in fact making more requests than you think it is, or you're on a network where there's some other source of high-frequency requests. You're not supposed to have to deal with this situation in general, because this isn't an API error - it's an error from the load balancer because your IP is generating incoming ...


3

So, this was a fun one. :) We apparently broke several different things over the course of a year that went unnoticed until Google turned off OpenID support. In no particular order but for fun and posterity: Facebook OAuth authentication just straight up didn't work. It broke back in January of 2014 when the code was accidentally changed from function ...


3

Although it doesn't appear to say so in the doc page, intitle expects an exact phrase, not a list of words. You can currently see this by: /2.2/search?intitle=get column array&site=stackoverflow which currently returns one result with that exact phrase in the title, but doesn't return the many questions that have those 3 words in other arrangements. ...


3

If the code tags are <pre>s, then \n is fine. Pre means "preformatted;" it makes the browser ignore the usual rules and preserve whitespace, etc. Repeat after me: "There is no such thing as a special character." Html is perfectly happy to receive UTF-8.


2

This is a very minor bug in the documentation page. The online doc page adds a convenient hyperlink to the post (The link part is not in the API's JSON response). That's a good thing. Most of the time this is rock solid, but notifications span all Stack exchange sites and the API doc pages normally only expect one site at a time. When the page is making ...


2

There is no difference and... The inbox has always been "The global inbox". Certainly for as long as the API has existed. So any inbox route will be Stack Exchange wide, even if it accepts a site parameter. If you look at the doc for the /users/{id}/inbox/unread route, it says: This method is effectively an alias for /inbox/unread. It is provided for ...


2

I faced the same issue when I was using the stack exchange API to post a message to stack overflow website. I figured I had to post my application on a domain name. I hosted my application on free domain provided by 000webhost.com. You may wish to take a similar approach. After deploying the application on the domain, change the oauth domain and the ...


2

This seems to have been silently/magically fixed in the last 7 months (Date of Nicos Karalis' comment). Descriptions seem correct now. I had verified that they weren't correct when I upvoted this question on Apr 29 '14. Side note: It's not documented, but apparently tag-based badges are not listed unless they have been awarded at least once. Take a ...


1

Annoyingly, the problem was here: (url-request-method "post"). Changing that to (url-request-method "POST") fixes everything.



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