Hot answers tagged

9

You need to encode the # character (to %23) http://api.stackoverflow.com/1.0/questions?title=true&tagged=c%23


5

Update: Version 1 of the API is long shut down. Here's sample paging on API version 2: /2.2/tags?page=1&pagesize=100&order=desc&sort=popular&site=stackoverflow /2.2/tags?page=2&pagesize=100&order=desc&sort=popular&site=stackoverflow etc... Obsolete, version 1 answer: ...


5

Inline tag edit requires 10k rep, but 2k rep is enough to edit questions (therefore, do retags). However, inline API is much easier - you just do the post, which contains tags only. Doing full edit requires accessing postable questions body. I've done quick modification to your script. It's a draft, but working for me... it activates edit mode, waits until ...


4

I agree. So it is written, so it is done. Behold, no wrapper posts.


4

That information is available in the /tags/{tags}/wikis route: "Returns the community editted tag wikis associated with a set of tags." Example: http://api.stackoverflow.com/1.1/tags/html/wikis


4

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


3

Related tags were one of the "maybes" slated for API V2.0. It got implemented today. Note that our definition of related is pretty much "appears on the same questions as", there's no real secret sauce there.


3

I'm new to the API also, I think mostly multiple args are separated with ; Try c;java


3

This is very costly to do in the API and currently impossible for many combinations of tag and date (because it would require more than the 10,000 allowed API calls per day). I'll write more about that tomorrow (11/11 or 11/12 UTC). Meanwhile, perhaps a SEDE query will work? The query: Top Answerers, by your tags and your date range takes your date range ...


2

You can get that by using the questions/unanswered route with the tagged parameter.


2

The API supports the /search call, which only searches for an exact match within the title of questions. For more general searching, I believe the recommendation is to use a search engine. You can use their (Google, Bing, etc) APIs to search within a single site.


2

IIS ASP.net, by default, prohibits service of many file extensions, .cs is one. So the request is being killed by IIS ASP.net before it hits the REST handlers. This can be fixed fairly easily by striking the following entry, if so desired... %SYSTEM%\Microsoft.NET\Framework\v2.0.50727\CONFIG\Web.Config .... <httpHandlers> <add path="*.cs" ...


2

Tags on the sites are, at most, 25 characters. Permitted characters are a-z 0-9 + # - . However, this is not part of the API contract insofar as if the site definition of a tag changes so will the API's. It is advisable, for correctness, to have a code path to handle tags > 25 characters in length. Simplest would be to truncate them. All that being ...


2

Normally, I am the one arguing for more data but in this case I will anticipate (and agree with) Kevin's likely response: The tag meta is not relevant to a question and inclusion of tag meta would be a significant increase in response data as well as requiring an additional join into the tag table increasing the execution cost of generating the response. ...


2

No, there's no API route that gives you a user's tag specific reputation information. The /users/{ids}/tags route only returns the combined count of questions and answers that a user has posted in a tag, but not the reputation information that you can get on the user profile tags tab. (Note: There's an app at Badge Status for a particular Tag in ...


2

This has been fixed. There was effectively a missing where clause on that route. Very odd.


2

For those who prefer Opera, you can create a simple CSS file to auto-hide ignored tags (not just grey out those tags) ... .tagged-ignored { display: none !important } Call it SE.css and save it somewhere - then tell Opera to use it for your SE sites. (need to set it per SE site). Enjoy!


2

As a result of some typos, those fields were being queried for... and then discarded immediately. A fix has been deployed.


2

No, we won't be implementing this. Not that I don't see a use case for it, but we'd never be able to accept and execute arbitrary regular expressions against the database. It'd just be far too easy cripple performance wise (we've done this accidentally plenty of times, and we don't have to worry about malicious actors on the dev team). While we could ...


2

Hear! Hear! I want to study what makes a good answer on SO. I started by querying complete web pages (questions with all comments, answers, and their comments) for questions with some minimum score (such as 5) for a number of fixed tags A,B,C created in some time period (say, one full week two months ago). This can be done well with \search and a filter ...


2

The tag object now has a has_synonyms field which is true when there's at least 1 approved synonym for a tag.


2

It's because tag ids aren't stable, so you can't reliably use them in the API. The same reason sites don't have ids. You'll note that most everywhere in the site's when we refer to a tag, we refer to it by name. Only when editing a few things do we expose the tag id, and those links can safely break.


2

Reputation gains from suggested edits are no longer returned by that route.


2

This should be fixed now.


2

This has been fixed.


2

First, you'll want to go upvote the feature request to add tag search for answers, etc. (If/when you have the upvote privilege) In the meantime, for answers by tag you can use the /search/excerpts route as long as you include is:answer in the q parameter. For example:       ...


1

For questions tagged with all tags in a list (AND operation), use the /questions path. For example: /questions#fromdate=2013-01-11&sort=activity&tagged=ruby;git ~~~~~ For questions tagged with any tags in a list (OR operation), use the /search path. For example: /search#fromdate=2013-01-11&sort=activity&tagged=ruby;git


1

Kevin was nice enough to grant my recent feature request on this endpoint, so it now returns "paged" results instead of a static top 30. I'm guessing the documentation just wasn't updated to reflect the change. I've tested it (StinkingBadges is using this functionality) and can confirm that your test result is the current "correct" behavior.


1

Based on the information you've provided in your comment - I will now provide an example of how you might accomplish what you're looking to do. The tags can be retrieved from the API using the /tags route - a sample request for Stack Overflow looks something like this (notice the results are paginated - you will receive the first 30 tags according to the ...


1

Tag scores didn't really exist when v1.0 was released. They'll be in the next API version, barring any great difficulties in exposing them. Unfortunately the underlying data store has made this harder, not easier over time. Taking this off the planned list as that's no longer accurate.



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