I like the idea of adding a close reason for this. A custom off-topic reason, something like,
This is a placeholder question for an app that's still under development; it will be deleted within 9 days unless regularly edited to show progress on development. If the app is ready for others to use, follow the template and flag for moderator attention to ...
This is great. Love it. Thanks man!
Suggestions for additional taglines:
I'm so glad you asked me that, but I have no clue how to solve it. Have a Calvin & Hobbes strip instead!
I have no idea. However, legend has it that reading Calvin & Hobbes strips will increase your problem solving ability so maybe that can help you.
I have no idea. But here'...
Should we ask the dev team politely to enable Stack Snippets here?
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 ...
The Stack Apps home pages are not giving new users the best impression.
Several obsolete, placeholder, beta, and low-scoring apps and scripts are placed prominently there.
This is closely related to this feature-request, but I propose more possible workarounds here.
I propose that in order for a post to get on the homepages (...
Yes, you can post extensions here that don't use the API. There are several scripts/extensions/apps posted here that use undocumented interfaces(example) or even screen scraping(example).
The extension must make use of the API and/or enhance one or more Stack Exchange sites.
My opinion is that they probably do not help, but that could change if you post a large enough bounty and are somehow able to "advertise" it (maybe in chat) to enough people that can answer (or upvote your app) and who are not regulars on Stack Apps, but willing to join the site.
There are very few people who regularly visit Stack Apps. Of those, I ...
Yes, stackapps is different from any other StackExchange site in a variety of ways:
Most "Questions" are meant to be announcement / product pages for scripts, apps, and libraries.
To this end, note:
Stack Apps has special tags: app, script, and library to facilitate posting tools that use the API and/or enhance Stack Exchange sites.
These posts look like ...
There's no real expectation set for this, feel free to pick whichever option seems better to you.
I personally feel the tag is sufficient, but I could see how having it in the title might save some people some disappointment. My hope is that people will just finish their app and it won't matter much either way, so I'm not particularly concerned.
They are one and the same.
When the API was first announced (March 31st, 2010), it was temporarily called the "Stack Overflow API" -- even though Jeff said that the API would be "for all the trilogy sites".
Two month's later, when stackapps.com and the public beta were announced, the official name was already Stack Exchange API. There is no separate API ...
If you have TamperMonkey installed, this simple script should fix the problem:
// @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 ...
Yes, obsolete listings (script / app / library) should at the very least, be made obvious at a glance and ideally obvious in search results.
For reference, there are currently only 754 listings that are not placeholders (more on placeholders, below).
Delete sparingly; removing legacy content should be a last resort.
Posts can have historical value.
I would vote for the historical lock option.
Straight deletion is harsh and someone somewhere may still need the information.
Creating a custom close reason could conceivably see posts erroneously voted closed.
A warning would have to be consistently worded for all posts to avoid any possibility of confusion in future readers.
A comment, with the best will ...
Closing them would help the developers, as sites like GitHub make it much easier to track and act on issues.
However, I don't think we should/can assume that every Stack Apps user has an account on sites like GitHub -- they may not be developers and are just casual users. Although it's easy to make an account, I don't think we should force them to!
If we ...
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
i have a doc scraper that produces json schema and smd. eventually it will be published as a service on SOAPI2.com, much the same way that soapi.info provides meta for v1.
but until then you can find the meta files here: https://github.com/bitpusher/SOAPI2/tree/master/src/SOAPI2.DocScraper/js
this meta is what i generate routes and model for soapi2 from, ...
Users on meta sites inherit from users on main sites, but not every main site user will have a meta account.
Meta users are spun up "on demand", the trigger generally being the first time a user visits a meta site.
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:
Broadly speaking, yes it's OK.
Stack Apps is for supporting the API, which includes meta discussion about it.
If things become too noisy we may have to move or restrict meta discussion; there's something of a hierarchy of importance that goes bug > support > feature-request > ... > meta discussion. Should meta discussion becomes detrimental to the other ...
This is either a bug or an incomplete feature. See:
What is the 'rev' dropdown supposed to do?
Stack Exchange Revisions Dropdown Does Nothing?
This extra dropdown seems to require:
That the post have had previous edits.
That the page mode editor is invoked.
This editor is the default for low-rep users under at least some conditions. (low rep still ...
First, read and thoroughly understand both:
What topics can I ask about here? (Stack Apps)
What types of questions should I avoid asking? (Stack Apps)
That said, you can propose changes to the API, or request apps, or request scripts.
Keep in mind that this site is not an app/script writing service and almost everyone here is a volunteer.
It would be ...
This isn't really a place to code-review your script, even if it uses the API.
Here is were you would publish your script1.
However, after a quick glance at the code, I don't see any glaring problems.
But, if you start making lots, or rapid, calls you will need to check and respect the backoff value and the quota_remaining value.
The API documentation is ...
Yes, the homepage is not showing Stack Apps in its best light.
As a mitigation that we can all do now:
Prepend "OBSOLETE - " or "PLACEHOLDER - " to the title, if appropriate.
(In addition to those 2 tags.)
Note that Power users can grey out or hide such questions: