Tag Info

Hot answers tagged

6

I don't see any particular reason not to add it, but there are some workarounds you can use in the meantime: Build a cache of all site information with the site URL as the key, and then look up the api_site_parameter value (and associated information) that way. or Use the fact that the domain name can be passed in as the value for site, and clean up ...


4

No, it currently does not. This has been discussed before, and if you really think it needs to be included in the API, you can vote for my feature-request here.


2

This is because the user hasn't specified a username on those sites yet. The name you see on SuperUser, for example, is somehow derived from his/her OpenID.


2

Confirmed: http://stackauth.com/1.0/users/febfb878-3f6f-4215-9323-46d15d62ac7d/associated Edit: I discovered this affects StackCenter too. Some of my accounts show a funny blue picture because the email_hash isn't being passed along.


2

This has been fixed. Site enumerations have changed alot behind the scenes in anticipation of Area51 sourced sites, and stackauth happened to get broken for a little bit.


2

Joel is pulling some (non-malicious, but unusual) tricks with his OpenIds and e-mails. This has a nasty habit of tripping up association related code. Improvements are naturally ongoing, but its not surprising that he tends to find new edge cases for us. Anyway, this particular issue has been fixed, although as a consequence of his SO association being ...


1

You get it from the users route, like I told you in your last question. You can't use the Id from the stackexchange website. But in version 2.0 of the API you will highly likely be able to again.


1

Unfortunately, there are no performance savings to be had if reputation is returned; this is simple the way the Stack Exchange network works at the moment. I will say that I'm hoping that by API 2.0 it will have become much cheaper to lookup associated user details, if so reputation will certainly be back in the 2.0 timeframe as a default. If it remains ...


1

This has been fixed.


1

Ah, there were recently some association changes on the main sites and this is a consequence of that. The API is not meant to return association information for Area51 (and Area51 doesn't expose an API itself). This has been fixed; such data is no longer returned.


1

This has been resolved. The /sites route got some tuning... and then some untuning, and general unpleasantness all around. As a side effect this route wasn't behaving correctly, and since the /sites route sees much more use I only got around to this one an hour or so ago.



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