Skip to main content
14 votes

Stack Exchange thinks that Shog is a elected moderator

Funny story... When I first joined the team here at Stack Exchange, Jeff just went around on the trilogy sites and made me a moderator... And he used the "elected" route instead of the "...
Shog9's user avatar
  • 641
7 votes

After successfully retrieving 180 pages, the API gracelessly, semi-silently, fails

Yes, this is a serious bug. You can replicate it from any browser using the code below. Every time I run it, it fetches 180 pages at an average rate of 5.51 calls per second. On the 181st call I get: ...
Brock Adams's user avatar
6 votes

The answer object returns an empty array for tags

This is a bug and seems (based on a series of A/B tests) to be linked with the body_markdown property. That is, if your filter returns the tags array, it works: "items": [ { "tags": [ "batch-...
Brock Adams's user avatar
5 votes
Accepted

Stack Apps homepage truncates user names

Recently the user name truncation issue has been fixed in the Stack Apps site, now it is looking good. Screenshot for reference:
Arulkumar's user avatar
  • 578
5 votes
Accepted

Bug with `badges/name` endpoint

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 ...
Jon Ericson's user avatar
5 votes
Accepted

"Informed" badge shown as Next badge, but doesn't exist on this site

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 ...
Arulkumar's user avatar
  • 578
5 votes

400 - Bad Request - Invalid URL errors with HTML response

This is fixed. I was able to pin down the issue two web servers. After SRE verified that the URL length settings were fine, I was able to narrow the issue to individual path components over the IIS ...
Brian Nickel's user avatar
5 votes

Suddenly getting "Couldn't parse `client_id`"

I expect this to be solved by Cloudflare protection is triggering on Stack Overflow authentication API routes To reproduce and/or verify this you can use this glitch app for which you can find the ...
rene's user avatar
  • 2,762
4 votes
Accepted

JavaScript SDK-based workflow never pushes message back from OAuth login_success page on Stack Exchange side

Thanks for the report. This has been fixed; for example you can see that the login demo is working properly again.
Jeremy's user avatar
  • 781
4 votes

Stack Apps homepage truncates user names

If you have TamperMonkey installed, this simple script should fix the problem: // ==UserScript== // @name SAHPA (Stack Apps Home Page Aligner) // @namespace http://tampermonkey.net/ // @...
anonymous2's user avatar
4 votes
Accepted

“Try It” URL has wrong URI

The link is correct. The purpose of that control is to provide a URL to the doc page with all the parameters prefilled. This is what most users expect and is similar to how that link control works ...
Brock Adams's user avatar
4 votes

503 errors on batch get questions endpoint

So, you are making up to 150 requests in a 30 second period (10 "parallel requests", with a 2 second pause in between). And failing at 80 to 100+ seconds of operation and 400 to 500 total ...
4 votes
Accepted

StackApps Captcha doesn't work: "Invalid domain for site key"

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!
Adam Lear's user avatar
  • 358
4 votes

'Informed' badge doesn't exist on site, but is still being promoted

I agree it is weird that you get teased for a badge you're unable to earn. It is worth mentioning that Stack Apps is a bit special as a Question and Answer site within the Stack Exchange family of ...
rene's user avatar
  • 2,762
4 votes

'Informed' badge doesn't exist on site, but is still being promoted

The button won't be shown after the next production build. Thanks for the report! The status-review tag will become red at the same time.
Adam Lear's user avatar
  • 358
4 votes

Items response empty after article POST request

The API for Teams behaves differently depending on the tier you're paying for: Free tier - No API access Basic tier - Read-only API access Business tier - Read/Write API access Additionally, only ...
Juice's user avatar
  • 186
3 votes

What happened to the links to a Stack App mentioned in the documentation about write access?

This is a documentation bug in my opinion. The "via Example App" was never included, nor should it be. A user is fully responsible for his or her content, it doesn't, and shouldn't, matter how that ...
Brock Adams's user avatar
3 votes
Accepted

Typos in API documentation

These were just fixed in the latest build.
Taryn's user avatar
  • 191
3 votes
Accepted

Invisible text in Markdown syntax help

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:
Arulkumar's user avatar
  • 578
3 votes

Why is "body" missing from certain inbox items?

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:
Brock Adams's user avatar
3 votes

API stopped allowing CORS requests

The bug has been fixed: Thanks for reporting. We're working on porting our websites to ASP.NET Core, and those errors you've seen were a result of this. We caught the first error ourselves on a ...
double-beep's user avatar
3 votes
Accepted

Please migrate the question templates to CommonMark

It looks like this has been fixed. Here's how the templates currently look like: <!-- thumbnail: https://example.com/some-image.png --> <!-- version: 1.0 --> <!-- tag: a-tag-on-the-...
double-beep's user avatar
3 votes
Accepted

Even though status-review has been made a moderator-only tag, it remains blue on this post

Yes, an edit will fix that. This is because posts are stored as HTML. At the time the answer was submitted the build wasn't live. Therefor the tag wasn't a mod-only tag yet. It got no special handling....
rene's user avatar
  • 2,762
3 votes
Accepted

Collectives Articles endpoint broken

The endpoint was for Stack Overflow for Teams and the Articles feature within that product. It returned Collectives Articles as an unintended side effect. When Teams moved over to a separate API, this ...
Berthold's user avatar
  • 146
2 votes
Accepted

top-answerers / top-askers documentation bug: number of results returned incorrect

Ok, this'll be corrected after the next API build.
Shog9's user avatar
  • 641
2 votes

Stack Exchange OAuth2, explicit access-token response format does not adhere to RFC6749 standard

I had the same problem. According to the authentication docs‡: In order to get access_token and expires (if applicable) wrapped in a JSON object, POST to https://stackoverflow.com/oauth/...
user84207's user avatar
  • 115
2 votes
Accepted

Few typos in the documentation pages

The fixes for this were just pushed in the latest build. Thanks for reporting it.
Taryn's user avatar
  • 191
2 votes
Accepted

Typos on api.stackexchange.com/docs/js-lib

Fixed, thanks to ᔕᖺᘎᕊ, for bringing it to my attention, rolling out in next API build.
m0sa's user avatar
  • 206
2 votes

Paging fails at 10K items for /search on any site but Stack Overflow

This was a search issue in elastic (max_result_window) that has now been tuned across the network. See, also, this related Q&A on Meta SE.
Nick Craver's user avatar
  • 2,194
2 votes
Accepted

/questions returns wrong markdown when a suggested edit is improved

This was an old, old bug: a bit of logic assumes that revisions can be ordered by their creation date. This is not true for Improved edits, as both the suggested edit and subsequent Improvement share ...
Shog9's user avatar
  • 641

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