5

This was fixed in the latest deploy.


5

I don't know for sure what the original problem was, but the most recent issue was a result of implementing a new badge without rebuilding the API. Once the API was pushed to production, the bug was resolved. If it happens again (especially if there's a new badge) please let me (or really any employee) know. We can contact a developer directly. From a ...


5

Recently the user name truncation issue has been fixed in the Stack Apps site, now it is looking good. Screenshot for reference:


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


4

The flag I think you're referring to was a recommend closure flag, which results in the post going to the Close Votes queue – not the actual flag queue, which currently has no backlog. Our flag response time is pretty good at the moment, sitting at a little under two and a half hours. It had recently been even better than that recently, but I've ...


4

If you have TamperMonkey installed, this simple script should fix the problem: // ==UserScript== // @name SAHPA (Stack Apps Home Page Aligner) // @namespace http://tampermonkey.net/ // @version 0.1 // @description Aligns the user names on the StackApps Home Page // @author anonymous2 // @match http://stackapps.com/ // @grant ...


3

Fun one. Changes behind the scenes to how closed reasons are handled caused the API to stop getting a real reason and start getting a null one. This was just different enough from failing to get a reason that it went unnoticed, oy. This was fixed in the most recent build.


3

This has been fixed with the latest deploy. There was a bug introduced in our move to elastic search where min/max was applied after paging results, instead of before. This meant that in any question that would typically have a lot of out-of-range results, the first page would tend to be culled down to nothing.


3

The documentation was updated sometime in the last 2 years and the API docs (version 2.2) now state that the property may be absent:


3

Update: Per Kevin Montrose's answer and its comments: The bug has now been fixed and the is_answered property will return true if either of these is true: The question has an accepted answer The question has an answer with a score > 0 To detect just whether a question has an accepted answer, merely check that the accepted_answer_id property is present and ...


3

We moved from nginx to HAProxy for our SSL provider this weekend as part of a larger rollout. In the move, we shifted our header checks to the now de-facto standard SSL protocol header. While I thought I fixed all the apps relying on the old header and standardized everything internally, stackexchange.com was left out and thought your auth requests weren't ...


3

This was fixed in the latest deploy.


3

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


3

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.


3

This design issue has been fixed in the How to Format section. Currently the text is visible correctly: ► backtick escapes `like _so_` Screenshot for reference:


3

The Informed badge is removed from the "Next badge" tracking. Previously it was listed in the Available badges section. Now it is not available under the Available or Bronze section. So the bug has been fixed recently. Screenshot for reference: Copied from the MSE answer


3

These were just fixed in the latest build.


3

Yes. I would agree that the tag serves no purpose. With only 24 questions, let us lose it.


3

Based on a reasonable response for Stack Apps, this has now been done. Merged stack-exchange into support (which many of the questions already had) and deleted support from those posts where it didn't apply. These 24 questions were affected:     2332, 2371, 2372, 2373, 3045, 3136, 3408, 4457, 4617, 4699, 4888, 4942,     6155, 6189, ...


3

Captcha wasn't configured correctly for Stack Apps on our end. The issue has been fixed. Sorry for the inconvenience, and thanks for the report!


2

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


2

Ok, this'll be corrected after the next API build.


2

This was fixed in the latest deploy.


2

Write methods have been added to an unreleased version of the API that's used by the official (albeit in-development) Android app, so it's expected that they'll be made available at some point after that app (and perhaps the one for iPhone) are released to the general public. …which has now happened. Various write methods are available as of the 2.2 ...


2

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

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

This was fixed in the latest deploy.


2

Okay, I didn't quite do what you wanted, but hopefully you'll find the solution I came up with acceptable. user-script is now a synonym of script, and I went through and retagged all questions that were about userscripts (but weren't posts intending to make a script available) with just scripts. Admittedly the distinction may not be immediately obvious to ...


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