Hot answers tagged users
4
Actually, I think I figured out a way to do this. If you specify the following:
/users?filter=john&sort=name&min=john&max=JOHN
That is, sort by name with "min" and "max" both set to "john" then it returns only those people whose name is exactly John. I wonder whether this efficient for the backend to process? It seems to respond pretty ...
3
Querying Stack Exchange Users
You may leverage the Filtering and Sorting capabilities of the Ajax grid to shape results based upon the entire Stack Exchange user base.
You may export the contents of the current grid page to CSV.
2
JSON API
Note:
I am just one developer and I do not have the time/money/resources to maintain an industrial grade public data source. If it is determined for any reason that you are not using the API in the capacity and terms indicated, your IP will be banned with a quickness.
I will shortly implement a private key system. Those interested in using the ...
2
Find Stack Exchange Users By UserName OR Email
You may find any user in the Stackiverse by the email address they supply when registering on any Stack Exchange site or by full or partial user name (display_name).
JSON API
{
"email_address": "foo@bar.com", // yes - this is a real account
"items": [{
"site_url": ...
2
As with suggested edits*, tag wikis, privileges, and so on... we don't expose things in the API until they've settled down quite a bit.
Also, "Whole network" APIs are something that take a bit of work to get adequately performant. A lot of effort went into getting the network profile pages to scale properly, similar effort will be needed on the API for ...
2
Liking it so far.
Here are some ideas. No idea how practical they are.
I'd really like a page which could tell me the latest activity of all my favourite users, maybe with a clever filter to remove the uninteresting stuff (badges, edits, accepts).
My browser just popped up a window for a fraction of a second. Please tell me that wasn't you...
Note that ...
1
The creators' ideas for future improvement - if somebody actually uses the plugin, we'll possibly implement some of these:
Possibility to configure a different color for every SE site (because one-color-for-all approach is working, but there's no single color that would fit all of them nicely).
Possibility to configure a different color for any user. Make ...
1
Not that this will solve you're main problem, but that actually isn't part of the API. If you go to api.stackexchange.com you kind information on how to get the data "raw", in JSON format.
Sadly however the API doesn't let you get reputation changes for multiple days at once, so you're still stuck with making lots of GET requests.
(I'm curious how you ...
1
You need to pass your request key as well.
I'm not sure what you're using that isn't giving you the error message back, but if you had captured it you would have seen it said something like:
{
"error_id":405,
"error_name":"key_required","
error_message":"`key` is required when `access_token` is passed."
}
1
StackAnywhere has so far not attempted solve this problem. A similar issue exists for question lists. In fact it's more likely to be an issue here because when the list is sorted by date, new questions can push others down the list resulting in duplicate entries.
It's an open issue in the StackAnywhere bug tracker at the moment.
1
association_id appears in the returns of /users/{ids} for user's who have existing associations.
For example:
... more ... "
up_vote_count": 871,
"down_vote_count": 48,
"accept_rate": 82,
"association_id": "f403b833-81b1-421c-96e6-ede6e9efb3c4",
"user_questions_url": "/users/80572/questions",
"user_answers_url": "/users/80572/answers",
...
1
As a sort of quick experiment, I slapped together a regex scraping of a single user's accounts page on SE.com and have put it up on the test deployment of se-flair:
http://test.se-flair.appspot.com/SEaccounts/[assoc-id]/
The return is, at the moment, a JSON object with the display name, the gravatar URL, and an array of sites, where each site has the ...
1
Drill-Down
An evolving feature of the StackApps platform is drill down on any user. The utility and polish of the features are somewhat affected by the fact that I am cutting my teeth on the completely different, and refreshing, paradigm that MVC presents. So bear with me. And email me suggestions as to what you would like to see.
Current features
...
1
Client-side Live Updates
With 370,000 rows of user data to maintain, it is an impossible task to keep every record updated up to the minute.
To mitigate relatively stale data on volatile fields such as last_access_date,
StackUsers offers optional client-side updates of results using Soapi.JS2.
You must opt in by either clicking the Enable Live Update ...
1
CSV output
Any grid on StackUsers provides an Export CSV to Clipboard button that will copy the data from the current grid view. This includes all user fields, not limited to those shown in the grid.
The output is standard CSV and can be opened or consumed by any tabular data editor.
Anonymous StackUsers can page 50 rows, while registered users are ...
1
http://stackapps.com/faq
http://stackapps.com/questions/2/getting-started-with-the-api
http://api.stackoverflow.com/0.8/help
Only top voted, non community-wiki answers of a minimum length are eligible
