We're experiencing problems with Twitter's OAuth login. After the
"Redirecting you back to your application..." page, we get a 500
error:
"Internal Server Error
The server encountered an internal error or misconfiguration and was
unable to complete your request.
Please contact the server adminis
I guess I might as well beg for those error messages while I'm at it.
If someone might be so kind as to post all the possible 403 messages,
it'll save me 7 hours of work (and possibly a suspended twitter
account) trying to get those messages.
On May 23, 6:06 pm, akaii wrote:
>
There seem to be a variety of possible causes for getting an 403 error
in responses to a calling statuses/update... you could be duplicating
a tweet or hitting the update limit for an hour or for the day.
How can you tell which one these errors actually occurred?
The only 2 ways I can think of is
I'm having no problems with sending an update directly via
https://api.twitter.com/, but the app (for the Iphone, I'm using
NSURLConnections) I'm working is supposed to allow the user to select
a preferred proxy (e.g. https://twitter-proxy.appspot.com/api/ or
https://nest.onedd.net/api/), and I kee
t;
> Brian Sutorius
>
> On Apr 29, 6:07 am, Raffi Krikorian wrote:
>
> > the numbers are roughly broken up over the day. and the limit applies to an
> > account.
>
> > and yes - there is a whitelisting for status/updates -- please e-mail
> > a...@twitter to ask
e roughly broken up over the day. and the limit applies
> > to an
> > > > account.
>
> > > > and yes - there is a whitelisting for status/updates -- please e-mail
> > > > a...@twitter to ask for it.
>
> > > > On Thu, Apr 29, 2
This is what the FAQ has to say about status update limits:
Updates: 1,000 per day. The daily update limit is further broken down
into smaller limits for semi-hourly intervals. Retweets are counted as
updates.
I'm a little unclear as to what exactly is meant by "further broken
down into smaller l
