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


6

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 Stack Apps will show up in your Community Bulletin main and meta too? community bulletin now is here for you!


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

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


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

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!


4

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.


3

These were just fixed in the latest build.


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

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

@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, but we do have a unique error message as compensation:


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

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

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. Please let me know if you see any other problems. Thanks for the report, and my apologies for the delay in fixing the issue.


2

The fixes for this were just pushed in the latest build. Thanks for reporting it.


2

Fixed, thanks to ᔕᖺᘎᕊ, for bringing it to my attention, rolling out in next API build.


2

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 the same date... So you'd get the wrong markdown. I've resolved this by falling back on ID to order, which is how we do it most other places. This may not ...


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