bump
On Dec 22, 9:31 am, Corey Ballou wrote:
> So... did this make it's way to the bug tracker? Is there any
> clarification if not?
>
> On Dec 21, 9:37 am, Corey Ballou wrote:
>
> > API call:
>
> >http://search.twitter.com/search.json?q=&ands=keg&geocode=35.22708600...
>
> > On Dec 20, 7:31 pm,
So... did this make it's way to the bug tracker? Is there any
clarification if not?
On Dec 21, 9:37 am, Corey Ballou wrote:
> API call:
>
> http://search.twitter.com/search.json?q=&ands=keg&geocode=35.22708600...
>
> On Dec 20, 7:31 pm, Corey Ballou wrote:
>
> > It's also worth noting that while
API call:
http://search.twitter.com/search.json?q=&ands=keg&geocode=35.22708600%2C-80.84312600%2C5mi&lang=all&result_type=recent&rpp=50
On Dec 20, 7:31 pm, Corey Ballou wrote:
> It's also worth noting that while the above example may not be pulling
> a place, the API call I'll be includi
It's also worth noting that while the above example may not be pulling
a place, the API call I'll be including tomorrow uses the latitude/
longitude pair pulled from the Google Maps API V3 geocoder with the
same outcome.
On Dec 20, 7:22 pm, Corey Ballou wrote:
> Here's my non API call searches fr
Here's my non API call searches from search.twitter.com with a 5mi
range:
keg near:"121 W Trade St, Charlotte NC" within:5mi
http://search.twitter.com/search?q=+keg+near%3A%22121+W+Trade+St%2C+Charlotte+NC%22+within%3A5mi
http://search.twitter.com/search?q=&ands=keg&phrase=&ors=¬s=&tag=&lang=all&f
