| bio | website | stackexchange.com/users/… |
|---|---|---|
| location | United Kingdom | |
| age | 18 | |
| visits | member for | 3 years |
| seen | 21 hours ago | |
| stats | profile views | 121 |
I'm a 16 year old from the UK whose learning my way around the programming world. Interested in physics, electronics and IT as well. My aim in life to get somewhere in programming or become an astrophysicist, and live into 2100.
Currently making an iPad app for stackexchange sites, which intenses to be part of the learning process only as I dont have an iPad. But now is getting closer to becoming a complete app, pushing me to save up for an iPad.
|
Jun 1 |
accepted | display_name isn't always there (should have OpenID name if needed) |
|
Jun 1 |
asked | api.stackoverflow/0.8/questions now gives answers as well by default? |
|
May 31 |
revised |
display_name isn't always there (should have OpenID name if needed) deleted 143 characters in body; edited tags; edited title |
|
May 31 |
awarded | Student |
|
May 31 |
comment |
display_name isn't always there (should have OpenID name if needed) ok, but that situation is very rare, and in the rare instances that happens text like "Unknown User" can be displayed. If I'm not to rely on the display name then when there is the list of questions what should I use for the question's asker (owner) |
|
May 31 |
comment |
display_name isn't always there (should have OpenID name if needed) I understand what everyone means by 2 names, but every user has a username, whether that's a display name or from OpenID, it's the name that appears under every question users ask. I don't understand why the API doesn't give the OID one when there no display name. It is already exposed on the site. And I could just go back to using a HTML parser and get everything from that, including the username. But this is long boring and takes up more of SO's bandwidth, and the user's download allowance. So there is no harm in returning the user's "username". |
|
May 31 |
comment |
display_name isn't always there (should have OpenID name if needed) No I think I just got a little confused about the incorrect username, just ignore that bit. |
|
May 31 |
comment |
display_name isn't always there (should have OpenID name if needed) Ok so the newbie-25 guy has asked one question. In that question it says the person who wrote that question is newbie-25. He doesn't have a display name so instead of the API returning nothing for display-nane it should return newbie-25 |
|
May 31 |
comment |
display_name isn't always there (should have OpenID name if needed) Ok so the newbie-25 guy has asked one question. In that question it says the person who wrote that question is newbie-25. He doesn't have a display name so instead of the API returning nothing for display-nane it should return newbie-25. |
|
May 30 |
comment |
display_name isn't always there (should have OpenID name if needed) No I'm saying that whatever the name of the person displayed in the actual question thread should be returned by the API. eg in this question it says "asked 3 hours ago Jonathan 101 @ 1" it should just return the Jonathan bit as the username of the question asker. So what ever the SO site displays in the question is what appears in the JSON file. |
|
May 30 |
comment |
display_name isn't always there (should have OpenID name if needed) this doesn't address the fact that the wrong users are being associated with questions. Also the API should return the username that appears on the question on the SO site. |
|
May 30 |
awarded | Editor |
|
May 30 |
revised |
display_name isn't always there (should have OpenID name if needed) added 145 characters in body; edited title; edited title |
|
May 30 |
asked | display_name isn't always there (should have OpenID name if needed) |