8

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 would always appreciate a minimal example, just to see outputs and how you might go about doing something, and it doesn't take too long to make a snippet! But it ...


5

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


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

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


5

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


5

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


5

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


5

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 default of 260 characters as described in https://stackoverflow.com/a/16903689/860000. SRE confirmed that UrlSegmentMaxLength was correct so there was only one ...


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


4

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!


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

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

This was fixed in the latest deploy.


3

These were just fixed in the latest build.


3

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 canary build and fixed it since it surfaced in the logs before deploying a full build. That full build contained the 2nd bug (no CORS headers), which we didn't see ...


3

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-post --> <!-- excerpt: Up to 200 characters of excerpt --> ## Screenshot / Code Snippet ... ## About ... ## License ... ## About ... ## Download .... ...


3

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 sites. We are more an "app store" then a proper Q/A site. I discussed with a CM and my fellow moderators the options we have. I personally wondered why ...


3

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.


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

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.


2

This was fixed in the latest deploy. The bug was basically selecting the wrong date to display (in this case, an associated post), and the right date for filtering and what not. Since not all badges are associated with a post, not all displayed dates were set and when they were set they were off by some (basically random) amount.


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

I would put a Snippet in this answer if I knew what to put in one but, thanks to Yaakov, this is now done. :)


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