Thanks Matt,
Two important implementation questions that aren't 100% clear from
that announcement or any supporting docs at this point;
1) "we are also restricting this permission to the OAuth /authorize
web flow only"
To be clear, does this include using the OAuth "/authenticate" method
as well
Hi folks,
Our service has been down for over 3 days now due to broken API calls.
Still waiting on any information from Twitter about what's going on,
but still in the dark.
About 3 days ago we started receiving messages (incorrectly in the new
error structure) saying "Over the limit for this typ
I'm getting some very strange intermittent errors when connecting to
the API. It's completely take down our app. It looks like connections
are getting reset intermittently. See a transcript below - the first
attempt it works fine, then second two the connection resets.
Sometimes it just hangs for m
The more I think about this situation, the less I like it.
At first I was happy that the service I work on was not banned by this
ToS change. Even though we use twitter data for monetisation, we don't
insert data into timelines.
However, when I look at the services that have now been banned, I
ca