Hello, fellow brazilian developer.
You should read the search API documentation. It says "you cannot use
the near operator via the API to geocode arbitrary locations".
To geocode a location (i.e., to get coordinates for a given city,
country or state name) you should take a look at the Google Ma
Hi Mark, I am just not there yet, 80% into the dev. If I can take
this off list, I would be more than happy to explain to you what it is
all about.
Thanks for the reply and working with me on this.
I plan on being public and getting a normal API key soon, as soon as I
manage to come up w
Scott,
Can you include the details of what you are attempting to do and how you are
going about doing it? 2500 uniques an hour is pretty strong, what site will
this application be running on?
Thanks,
Doug
On Mon, Jun 29, 2009 at 10:42 AM, Scott Haneda wrote:
> Reposting. I should have fixed t
Reposting. I should have fixed the horrendous spelling my phone dished
out. Sorry for the double post, but this one should be clearer…
Thanks. I have a feeling I'm going to go over the 20,000 a hour hit
rate limit. Are those hard limits or does Twitter make concessions to
busy sites?
I ca
Thanks. I have a feeling I'm going to go over the 20,000 a hour hits
rate limit. Are those gard limits or dies Twitter make concessions to
busy sites?
I can not have the use login, to much if a barrier. I figure each
visit is going to be at best 2 API hits, and at worst, maybe 4.
That's a
The search API only has 7 days of history available, currently. Try the REST
API for that user's updates.
-- ivey
On Mon, Jun 29, 2009 at 3:50 AM, talklists wrote:
>
>
> http://search.twitter.com/search.json?page=4&max_id=2384515303&rpp=80&q=from%3Acometbus
>
> I have hit page 4 on that reques
