The OAuth issue seems to be resolved on this end. Upon *not* being already signed into twitter, I can now use oAuth to authenticate and sucessfully fire back towards the callback ur li've set it up. So it seems like it's back working.
I"m on a development/local machine though so I'm not sure how this effects in production. On Aug 17, 7:26 am, Dewald Pretorius <[email protected]> wrote: > I'm not so sure that one can describe the relative silence on this > thread as patience. > > It can probably be ascribed to developers abandoning Twitter and being > too busy coding for other platforms to even bother writing on this > thread. > > To have exactly the same thing happen to third-party apps for two > weekends in a row, which causes high-volume API calls to be blocked > and the apps to be broken for days on end, is just simply pathetic. > That is NOT "developer support" in any way, shape or form. > > Not to mention the fact that again nothing is posted about it on the > Twitter Status blog, even after a request for such a post was made by > us. > > We are again left swinging in the wind by Twitter. > > Dewald > > On Aug 16, 2:55 pm, Jonathan George <[email protected]> wrote: > > > Please post an update to status.twitter.com, so our users can be as > > patient as we are. > > > best, > > jonathan
