New answers tagged

0

For trends like this, the Stack Exchange Data Explorer is a better option (if you know SQL; if you don't, check out the awesome tutorial). About the only downside is that it is refreshed once per week, on Sunday morning; the API gives you real-time results. The API would be able to provide the number of questions asked in the last week for certain tags, e.g....


1

You would need to demonstrate that your reviewing app contained sufficiently advanced AI to be able to correctly perform the review. Reviewing takes time and effort and involves checking many aspects of the post. This would be a major AI project. The risk of robo-reviewing or just plain making wrong decisions is too great. Consequently, the risk of ...


2

You're correct in assuming you need dedicated compression support; HttpURLConnection by itself won't be able to process the output. I'm not sure where your problem is, but let me help you with this simple example (using IOUtils from Apache Commons IO). The deCompress method isn't even necessary: if (responseCode == HttpURLConnection.HTTP_OK) { String s; ...


0

The changes in version of the API are documented in the Change log. For V2.0 it has the following info on the request URL: All API request now go to api.stackexchange.com with a site parameter Every method of the form /users/{ids}* now has a /me version, which is the same as calling the /users/{ids} version with the user id of the passed access_token passed ...


Top 50 recent answers are included