9
votes
Accepted
Wouldn't it be nice if we had a Community Bulletin?
Yes, it would. And now you do!
Pushed some improvements for your Community Bulletin experience:
No more "Stack Apps has no Site.ChildMeta defined" message
Posts with the featured tag on ...
8
votes
Should we enable Stack Snippets?
Should we ask the dev team politely to enable Stack Snippets here?
Yes!
It would, primarily, be useful in cases such as your example: support with using the API.
I think people looking for help ...
5
votes
Accepted
Should we "Burninate" the [stack-exchange] tag?
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'...
5
votes
Should we "Burninate" the [stack-exchange] tag?
Yes. I would agree that the tag serves no purpose.
With only 24 questions, let us lose it.
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 ...
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 ...
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:
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 ...
5
votes
Wouldn't it be nice if we had a Community Bulletin?
@Catija just informed us the Community Bulletin is now live. Because Stack Apps is ... special (it's a main site but also its own Meta, just like Meta Stack Exchange), we won't see posts featured here,...
5
votes
(Should we) add [Staff] labels to staff member flairs?
This request will be status-planned and we hope to have this completed in the near term in a future sprint.

tanj92Staff
- 151
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/
// @...
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!
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♦
- 2,275
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.
4
votes
Accepted
(Should we) add [Staff] labels to staff member flairs?
Tada! 🎉 This was an easy change on our end, it turns out we already had functionality to turn this on for individual sites. Our code doesn't define Stack Apps as a Meta site so Stack Apps doesn't get ...
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-...
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 ...
3
votes
Accepted
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:
3
votes
Accepted
Descriptions of tag-based badges are incorrect
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 ...
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:
2
votes
Implicit Flow Isn't Redirecting
Sorry about that. Turns out, return URLs were broken on stackexchange.com entirely during signup and login. A fix is out now, so any API app auth redirect issues should also be resolved with it.
...
2
votes
Accepted
Few typos in the documentation pages
The fixes for this were just pushed in the latest build. Thanks for reporting it.
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.
2
votes
Accepted
Login using Google fails saying OpenID 2.0 accounts for Google has gone away
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 ...
2
votes
Accepted
top-answerers / top-askers documentation bug: number of results returned incorrect
Ok, this'll be corrected after the next API build.
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 ...
2
votes
Accepted
Should we enable Stack Snippets?
I would put a Snippet in this answer if I knew what to put in one but, thanks to Yaakov, this is now done. :)
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.
Only top scored, non community-wiki answers of a minimum length are eligible
Related Tags
status-completed × 332bug × 254
api-v2 × 58
feature-request × 56
documentation × 51
api × 33
support × 28
meta × 25
discussion × 17
api-v2.2 × 13
tags × 13
oauth2 × 13
users × 12
stackauth × 12
api-v2.1 × 11
questions × 9
obsolete × 9
search × 9
authentication × 7
comments × 7
stackapps × 7
badges × 7
timeline × 7
associated × 7
answers × 6