ejecting whitelisting requests. That
> > reason should be in the body of the rejection email.
>
> > If you create a bunch of accounts, our spam team is likely to suspend
> > them. Please address the issues mentioned in the rejection email and
> > re-apply.
>
> > On T
Our users continue to complain about hitting API limits for our app. I
applied to get whitelisted, but got rejected. I'm thinking of creating
several "test" accounts that run the more intensive API call
procedures as cron jobs, to not use our users' api calls.
Any idea why we got rejected? (app n
m/th...
> [5] -http://code.google.com/p/twitter-api/issues/detail?id=265
>
> On Apr 14, 2009, at 09:31 AM, Brandon Geiger wrote:
>
>
>
> > Right now we are using the method:
>
> >http://twitter.com/friends/ids.json
>
> > to get a user's friends, but i
Right now we are using the method:
http://twitter.com/friends/ids.json
to get a user's friends, but it doesn't have the friend's screen_name,
which is obviously how users identify their friends. So what we are
currently having to do, is store the id's in our database then loop
through and use th
itter.com/dougw
>
> On Fri, Apr 10, 2009 at 11:49 AM, Brandon Geiger
> wrote:
>
>
>
> > We are debating whether or not we need to authenticate users when
> > making a call against the search API.
>
> > Thanks
We are debating whether or not we need to authenticate users when
making a call against the search API.
Thanks
you should follow @twitterapi - easier to keep up with announcements
regarding the API and OAuth. It went public the 16th.
On Mar 25, 2:21 pm, iematthew wrote:
> The last I heard, OAuth was still in closed beta. I'm assuming any
> announcements of an official launch would appear in the API
> Ann
Hey group,
Is anyone else experiencing issues getting a user's direct messages in
OAuth? I'm using Abraham's PHP wrapper (http://twitter.abrah.am/) to
make calls in OAuth. It seems like every single call that we make,
including sent direct messages, is working with the exception of the
user's di
