It's a bit of a Catch-22. Work around it by:
Make a app (or script) post for your app (or script).
Also tag it with placeholder.
And put "PLACEHOLDER -" at the beginning of the title.
Also, indicate in the post text that the app is not yet ready for prime time.
This has already been done a few times, for example:
"Chatdump - a site monitor (placeholder)"...
You should update your placeholder post to reflect the latest developments. You can use the template to know which information could be useful for potential users of your application. Otherwise, your placeholder question may be closed for the following reason:
This is a placeholder question for an app that's still under development; it will be deleted ...
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 ...
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 faced the same issue when I was using the stack exchange API to post a message to stack overflow website.
I figured I had to post my application on a domain name. I hosted my application on free domain provided by 000webhost.com. You may wish to take a similar approach.
After deploying the application on the domain, change the oauth domain and the ...
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 did ...
The "Manage API Keys" link takes you to your list of registered API 1.x applications. Since the 1.x versions of the API are now deprecated, you won't be seeing anything new show up there.
All new applications that you register for API 2.x will instead show on the "Manage your applications" page.
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
Flags here are being acted upon, it is just that sometimes they take a couple of days to be seen. No moderator on any site is expected to be active every day.
There are a number of the lower-traffic sites here in a similar position. That is, keeping going with only one or two moderators. I'm sure The Powers That Be are aware of this and will be ...
I get the reason:
Do not use gem 'omniauth-stackexchange', '~> 0.2.1' ,but instead of gem 'omniauth-stackexchange', git: 'https://github.com/nashby/omniauth-stackexchange.git'
The reason see this:add call back url
I think you can just create an app and mark it as a placeholder. Those are
for apps that don't quite work yet, but need a registered Stack Apps post for testing.
Incomplete posts are allowed for placeholder apps, so you don't need to fill in all the details. While this might be bending the rules a bit, as long as it doesn't cause an avalanche of ...
That data is stored as HTML in the database, as are more fields (e.g. the about_me field right above the location). Presumably, this is done for performance reasons. ü is the HTML entity corresponding to ü. You just have to decode the string; every programming language has a method for this, e.g. html.unencode() in Python.
By the way, it's strange ...