Thanks for the explanation. It's easy enough to parse, it just seemed
so bizarre (and I was having a bad oAuth day!). -ZPC
On Jun 21, 4:37 pm, themattharris thematthar...@twitter.com wrote:
The time format is a little weird and as far as I know, doesn't match
any RFC. Instead it matches the
*Question:*
I'm tweeting throught twitter for iPhone and geotagging each tweet.
When I try this search API query
http://search.twitter.com/search.json?geocode=-33.4135,-70.5999,10miq=danielatik
http://search.twitter.com/search.json?geocode=-33.4135,-70.5999,10miq=danielatikI
cannot see GEO lat,
The time format is a little weird and as far as I know, doesn't match
any RFC. Instead it matches the ruby default and is represented in
tokens by:
%a %b %d %H:%M:%S %Z %Y
The format has been like this since the API was first released which
means, for backwards compatibility with other
On Mon, 21 Jun 2010 13:37:12 -0700 (PDT)
themattharris thematthar...@twitter.com wrote:
The time format is a little weird and as far as I know, doesn't match
any RFC. Instead it matches the ruby default and is represented in
tokens by:
%a %b %d %H:%M:%S %Z %Y
which leads to the next
