Timeline for Encoding inconsistency on /users/{id}/reputation
Current License: CC BY-SA 2.5
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 10, 2010 at 7:05 | vote | accept | Felix | ||
| Aug 10, 2010 at 6:28 | comment | added | Sky Sanders |
@jjn - I don't think Felix is asking for anything. I think Felix is raising 2 good points 1) consistency is a virtue. 2) the data is JSON, not html. If a character needs to be utf encoded, so be it, but html encoding is not appropriate for any field other than body.
|
|
| Aug 10, 2010 at 6:09 | answer | added | Kevin Montrose | timeline score: 1 | |
| Aug 10, 2010 at 6:09 | history | edited | Kevin Montrose |
edited tags
|
|
| Aug 10, 2010 at 1:12 | comment | added | jjnguy | @felix, do you think your API should automatically return decoded Titles? | |
| Aug 9, 2010 at 23:53 | comment | added | Felix | @code heh, thanks for satisfying my lazyness and including the relevant bits of the json in the question :) | |
| Aug 9, 2010 at 23:13 | comment | added | Sky Sanders | It might be relevant that the text in question is a member in two distinct structures. | |
| Aug 9, 2010 at 23:12 | comment | added | Sky Sanders | @dennis - your clicker broken or sumpin? ;-) nice catch felix. | |
| Aug 9, 2010 at 23:12 | history | edited | Sky Sanders | CC BY-SA 2.5 |
added 127 characters in body
|
| Aug 9, 2010 at 23:10 | comment | added | Dennis Williamson | It would be nice to add the lines to your question. | |
| Aug 9, 2010 at 22:49 | history | asked | Felix | CC BY-SA 2.5 |