13

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


13

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


7

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


7

feature-requeststatus-planned 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 (...


6

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


6

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. Reference: Stack Exchange APIs Terms of Use (Still applies, for the most part) ...


6

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


6

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


5

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


5

Yes, stack​‌apps 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 ...


5

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


5

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 Alternatives: You can get real-time notifications by hooking into one of the undocumented ...


4

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.


4

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


4

bugfeature-request Can we get the home page to show all the tags for a post. And also, ideally, the post's score: EG, from: To:


4

Here is a GreaseMonkey script I threw together: // ==UserScript== // @name Old Comment Delete Button // @version 1.1.0 // @grant none // @author a stone arachnid // @include https://*stackoverflow.com/* // @include https://*superuser.com/* // @include https://*serverfault.com/* // @include https://*stackapps.com/* // @include https://*...


4

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


3

As long as you follow the guidelines Jeff laid out on Attribution Required you should be able to display as much content as you want. Visually indicate that the content is from Stack Overflow, Meta Stack Overflow, Server Fault, or Super User in some way. It doesn’t have to be obnoxious; a discreet text blurb is fine. Hyperlink directly to the ...


3

Each question on a Stack Exchange site already has a RSS feed. Just scroll all the way down the page, on the right-hand side you'll find a question feed link:


3

If the answer is the accepted answer, is_accepted is true and anyone can see it. accepted is set to true only if the currently authenticated user is the one who has accepted the answer. For instance, if I obtain an access_token with the private_info privilege and call: /2.2/questions/30028657/answers?site=stackoverflow&key={YOUR APP KEY}&...


3

Currently, the Stack Exchange API has nothing to do with Stack Overflow Careers. Anyway, there is no API for accessing Stack Overflow Careers job listings. Best you can do is grab the most recent 1000 listings from the Careers "all new jobs" RSS feed.


3

You should use /inbox instead, which is a network route instead of a site-specific one. As mentioned in the documentation, the site-specific route is mostly just provided for convenience of consumers working in a single-site context. Even then it doesn't seem particularly useful, but meh. To answer your question in regards to why site is required there, it'...


3

Sounds like you are technically not "linking" the pages (to open in Chrome, Firefox, etc.). Google suspects you of "bundling" someone else's content: We don’t allow apps whose primary purpose is to drive affiliate traffic to a website or provide a webview of a website without permission from the website owner or administrator. The overall Stack Exchange ...


3

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


3

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


3

I've written a simple script for this, called NSFW (because it shows content that is Not Suitable For Work). It will only work if you have 10k reputation (2k on beta sites); otherwise, you probably won't see the post anyway. The link to the revision history will be added to the 'post menu' with the share, edit and flag links. You can install it here (...


3

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


3

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


2

It depends on what profile information you need to display. Basically anything in a user's profile that's public-facing is exposed via the API and requires no action on behalf of the end-user. Starting with v2.0 of the API, you have limited access to some private user information (such as the their full reputation history) through the OAuth 2.0 methods. In ...


2

No, there isn't. We don't guarantee the javascript interfaces won't change (or that that dialog won't be radically altered). Generally speaking, if you want to mimic a piece of our UI you'll just have to re-implement it if you want it to be stable.


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