A hack is to pull their latest update and do a text comparison of the
status. This is not ideal though.
Abraham
On Tue, Apr 27, 2010 at 07:01, Spode sp...@justfdi.com wrote:
I've been having a problem I can't get work out.
When sending a status update or direct message - I often get a 0, 502,
503 or 420 response code. Yet the API suggests that status updates
aren't limited.
The annoying thing is that I'm assuming if I get one of those codes
that it was a failure - but in fact, the posts make it through. This
means I report falsely and people will try and post again - often
ended up with double/triple posts.
Any ideas?
Spode
--
Subscription settings:
http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
--
Abraham Williams | Developer for hire | http://abrah.am
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
