Mmmm. I can live with this for Six to Eight, because I'm planning an update this summer anyway. However, referring to http://blog.stackoverflow.com/2010/05/stack-exchange-api-public-beta-starts/ - the original "Beta begins" blog post - we find...
If you build to our API, we will support you. We’ll be on Stack Apps
daily helping out in any way we can, ...
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 ...
The OAuth domain name is the domain name that will be used to restrict the value of the redirect_uri parameter when authenticating from your application. This is done as a security precaution to prevent others from using your API key and redirecting to a domain name that does not match the one specified in the registration form.
The API documentation page ...
Unfortunately the news is bad all around.
Sathya has updated the tag wiki for script to include the following paragraph:
As of May/June 2012, Chrome no longer allows for direct installations of off-store extensions. To install them, you'll have to download/save the .user.js file, open chrome://chrome/extensions/ (or Click on Wrench -> Tools -> Extensions ...
It's allowed with the caveat there's no guarantee it won't be merged, provided that you abide by the good faith criteria.
If you attempt to actually run something like the script in your previous post, for example, both accounts will likely be suspended without second thought. Having a separate account for testing doesn't shield you from the consequences of ...
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 (...
You don't explicitly need permission, but you must follow certain rules and legal requirements.
Refer to Jeff Atwood ♦'s answer to "Etiquette of Screen-scraping Stack Overflow?":
We regularly block (IP range ban) unknown scrapers that do not identify themselves and/or have poor behavior patterns. These bans are permanent until someone emails us to make a ...
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.
You cannot get the days visited, nor consecutive, information for a user because that is private information(Poster is SE representative).
Stack Exchange is supposed to be about the content, not the people. And knowing people's (more detailed) visit history is a social metric, not an on-topic bit of information.
In a similar question, one power-user put it ...
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 ...
Since we're approaching feature freeze on V2.0, I guess it's time to lay down some guidelines here.
Henceforth on app, library, or script posts
should be used for
"bite sized" bug reports (it's down, doesn't work on XP, etc.; anything that doesn't need much context or is trivial to reproduce)
should be ...
the original question was apparently for V1.
in V2 we now have https://api.stackexchange.com/docs/required-tags
the request: https://api.stackexchange.com/2.0/tags/required?order=desc&sort=popular&site=stackapps will return required tags
See the "Safety" heading in the "Custom Filters" doc. The difference between a "safe" (default) filter and an "unsafe" filter, is that the unsafe data might return data that could result in a script injection if the data was directly inserted in an HTML document. (EG: '<script src="PwnYaSucka.com">...')
Some fields are apparently inherently devoid ...
Invalidate an access token doesn't log the user out of the sites themselves.
What you're seeing here is the user's global auth session kicking in. To completely log someone out of the Stack Exchange network (other than having them actually use the "logout" link), you need to clear cookies and local storage.
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 ...
I had the same feeling last year, so I started collecting all sorts of little interface fixes into a single script that I called the Stack Overflow Unofficial Patch, or SOUP for short.
Of course, SOUP is still very much a work in progress, and always will be. If you find something missing from it, I'm always happy to receive suggestions (and even happier ...
No, the WebSockets are not officially supported. They are internal to Stack Exchange, use them at your own risk.
If it is at all possible to do your task with the API, use that. That's what it's there for.
Some people have sussed out some of the endpoints. You can see them in the answers to:
How do the Stack Exchange WebSockets work? What are all the ...
Stack Exchange's markdown is just a variation of standard Markdown, so the MultiMarkdown editor may be enough of what you want.
MarkdownPad - a "fully featured Markdown editor with live preview". Developed by a SO aficionado.
Emacs Markdown Mode - a plugin for the common programming editor.
See, also, "Are there any text editors which are ...
To find user_id(s) for a username, use the inname parameter of the /users query.
You will have to repeat this query call for every Stack Exchange site that you are interested in. For example:
This is what preview is for.
Every write method takes a parameter called preview (the test console defaults it to true for testing purposes). When it's explicitly set to true, the method goes through all the validation it otherwise would but stops just short of actually committing the data. Preview calls also don't consume any of a user's write quota.
You might consider looking at StacMan for inspiration, a C# client that deals with some of these questions.
Off hand it does push everything through a "Manager" (called a Client in that code) and automatically enforces backoff and simultaneous request throttling.
How many requests are OK to send simultaneously?
While there is a strict cutoff... ...
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.
Probably the most cost-effective way is to poll /questions every minute or two. (Results are cached so, polling more than once a minute probably won't do anything but chew up your quota.)
Related: Provide a streaming API instead of forcing API users to poll
You can get real-time notifications by hooking into one of the undocumented ...
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.
You can register a callback with Stack Exchange Chat, which gets called prior to the change happening in the DOM (i.e. if you want to find a new message in the DOM, you need to use a setTimeout() to act after the DOM change). Callbacks can be registered with CHAT.addEventHandlerHook(callback), which takes a function as its single argument.
The callback ...
We're judging*, winners should be getting emails next week with a blog post to follow.
It was removed from the API homepage because the linked blog post was about entering the contest, and entry was closed at that point. A few people were confused about whether they could still enter, seemed best to remove it.
So, basically, stay tuned!