network profile
| bio | website | 2718.us |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 2 years, 10 months |
| seen | Apr 29 at 21:59 | |
| stats | profile views | 21 |
|
Jan 8 |
comment |
se-flair: HTML combined Stack Exchange site flair @Rory: There's some issue with the Skeptics site favicon that was causing the PNG image assembly to fail. I've patched the PNG generation to skip over favicons that fail in that way, so your PNG should work now, though that favicon is missing. |
|
Jan 7 |
comment |
se-flair: HTML combined Stack Exchange site flair The just-released revision that uses the account id instead of the association id should make se-flair work for you now. |
|
Jan 7 |
comment |
se-flair: HTML combined Stack Exchange site flair @Rory: I suspect you may have been hitting the same issue as Joost. If you try it now, you should get a different URL that works: se-flair.appspot.com/1098500 |
|
Jan 7 |
comment |
se-flair: HTML combined Stack Exchange site flair @Joost: New URL: se-flair.appspot.com/1893844 |
|
Dec 16 |
comment |
se-flair: HTML combined Stack Exchange site flair This appears to be the same issue that I already reported for another user, so I've edited that question to add your case as well. |
|
Nov 9 |
comment |
se-flair: HTML combined Stack Exchange site flair @Joost: My guess is that it's a glitch in the account-association data in some fashion, so I posted a question here asking about it: stackapps.com/q/3756/2490 |
|
Oct 30 |
comment |
se-flair: HTML combined Stack Exchange site flair @Joost: The association ID returned for your account by the API (v1.1) is apparently wrong or broken (from what the API returns, stackexchange.com/users/705af49e-38d2-1c16-b05a-f49e35176016 should be your SE-wide profile, but it's a 404 page). I'll see if there's any way that I can work around it later tonight. |
|
Mar 2 |
comment |
se-flair: HTML combined Stack Exchange site flair @Giorgi: It should be fixed now. |
|
Feb 11 |
comment |
Expose the contents of the “accounts” tab of the SE network profile as machine-readable data If this is status-completed, could you post an answer with at least a link to the relevant documentation (which I could then mark as accepted)? |
|
Sep 23 |
comment |
Expose the contents of the “accounts” tab of the SE network profile as machine-readable data @GeorgeEdison: That's good to know—I couldn't have forgotten it because I didn't even know a v2.0 was coming. I'll have to keep an eye out for it to keep se-flair working. |
|
Sep 2 |
comment |
Expose the contents of the “accounts” tab of the SE network profile as machine-readable data Would it be preferable from SE's perspective if I: (1) made a StackAuth API call followed by API calls to each site on which the target user has an account; or (2) scraped the accounts page of the user's SE profile? |
|
Apr 5 |
comment |
se-flair: HTML combined Stack Exchange site flair @umar: The only problem with doing it that way is that JSON-formatted flair is deprecated and may be removed at some point in the future. |
|
Apr 5 |
comment |
se-flair: HTML combined Stack Exchange site flair @umar: regex parsing/scraping of the profile page |
|
Apr 5 |
comment |
Newt - question, answer and comment and rep change notifications for Mac OS X @Nikita: I'm only seeing math.SE, SO, and meta.SO for mine, none of my other accounts' rep. When I paste in a profile URL, is it only using that site, or is it getting all associated accounts? |
|
Apr 5 |
comment |
Newt - question, answer and comment and rep change notifications for Mac OS X How are the accounts for which rep is tracked selected? |
|
Mar 7 |
comment |
Authorized requests: auth parameter seems broken @Kevin @systempuntoout: It just occurred to me that despite the number of timeouts I'm seeing on API calls to specific SE sites, I don't think I've ever seen a StackAuth API call timeout. I have no idea if this means anything, though. |
|
Mar 6 |
comment |
Authorized requests: auth parameter seems broken @Kevin: From the earlier discussion in the comments, I'd think it's on Google's end, too; I was just not entirely sure that what I was seeing with se-flair matched up to what you and @systempuntoout were talking about. Also, it's good to know that the rate-limiting is always a quick cutoff and never a slow-down. |
|
Mar 6 |
comment |
Authorized requests: auth parameter seems broken I don't know if it's related, but with se-flair (which also runs on GAE), I've been seeing timeouts (URL fetch didn't complete within 5 seconds) on maybe around 10% of API calls, seemingly at random. (I'd been assuming it was either rate-limiting-related or just that API calls sometimes took longer than 5 seconds.) |
|
Mar 6 |
comment |
se-flair: HTML combined Stack Exchange site flair One way is through se-flair: http://se-flair.appspot.com/[site hostname]/[user_id on that site]/ will find it and redirect you to http://se-flair.appspot.com/[association-id]/—for instance, for your account here, http://se-flair.appspot.com/stackapps.com/4684/ redirects to http://se-flair.appspot.com/db343971-bdd4-4dc5-997c-1adcf4ab2843/, so your association-id is db343971-bdd4-4dc5-997c-1adcf4ab2843. |
|
Mar 2 |
comment |
se-flair: HTML combined Stack Exchange site flair @chanchal1987: It should be fixed for yours now. I hadn't properly covered the case where the Area 51 account is the highest-rep account. |
