| Issue 206: | Unify date format between search and main api | |
| 1 person starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
What's the problem you're seeing? Dates are not universal among all the APIs... Public Timeline: Thu Dec 18 21:16:11 +0000 2008 Search API: Thu, 18 Dec 2008 20:37:30 +0000 Friends Timeline: Thu Dec 18 21:19:31 +0000 2008 User Timeline: Thu Dec 18 21:19:31 +0000 2008 As you can see, the timelines are fine, but why the totally different format with the search? Thanks, James Hartig |
||||||||||
,
Dec 18, 2008
To clarify, I think this is in relation to the JSON API. The search system was originally a different company (summize) and the formats were different. This date format as well a mis-matched user ids and missing fields are all slated to be corrected when we unify the two APIs with the next version of the API. I don't want to change the search format until then because it would require existing users to change code twice.
Summary: Search API date format does not match
Status: Accepted Labels: -Type-Defect -Priority-Medium Type-Task Priority-Low Milestone-V2 |
|||||||||||
,
Dec 18, 2008
Ah! Gotcha that makes sense :) Can I hear ahead of time which format you will plan on sticking to? :) |
|||||||||||
,
Dec 23, 2008
I'd like to standardize on RFC 822 (updated by RFC 1123) dates. We'll open that up to discussion when the time comes. Marking WontFix for now.
Status: WontFix
|
|||||||||||
,
Dec 23, 2008
Er, actually, sorry, marking for V2.
Status: Accepted
|
|||||||||||
,
Jan 08, 2009
Assigning to myself and making the title clearer.
Summary: Unify date format between search and main api
Owner: m...@twitter.com |
|||||||||||
,
Mar 09, 2009
If it helps, the Date.parse function in IE works only with the Search API date format (the 2nd one), and that's the one I'd prefer to see. Currently, I manually parse the date from JSON feed using Javascript so that IE can display it properly, whereas for other browsers (Chrome and Firefox) the format is irrelevant to it being usable to the Javascript engine. |
|||||||||||
,
Apr 04, 2009
Can't you guys make an extra field with the REST API's date format and viceversa? :-) |
|||||||||||
,
Apr 21, 2009
This issue has been recoreded in the future roadmap: http://apiwiki.twitter.com/V2-Roadmap
Status: Moved
|
|||||||||||
,
Apr 21, 2009
Marking "Invalid" so these issues don't clutter the main view of issues. All are tracked on http://apiwiki.twitter.com/V2-Roadmap
Status: Invalid
|
|||||||||||
 Sign in to add a comment
|
|||||||||||
