writing a tweet deleter, ran into issue where the lib I was using, their api wrappers would return the response on 200 or throwM it on 4xx
-
-
but it's simple! on success the thing is supposed to return a status object! so if you're wrapping with a catch that's what must come out
-
...sooo naturally I just fetch a status when the program starts and hold onto it to return from the handler every time it fails. as you do
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.