I know Twitter is still working on finding a fix but it's been a couple of weeks now and it might be a good idea to implement the https to http hack for now until they resolve the issue. I was hoping there would be a fix by now but I can't wait any longer so I will be making that change.
On Mon, Mar 28, 2011 at 11:30 AM, r9handa <[email protected]> wrote: > Are you guys still experimenting the issue? My application is still > very unstable, got the Unauthorized all the time. > Anyone knows if we have to change our application, or Twitter will fix > the problem? > Thanks. > > On 24 mar, 10:44, Ninjamonk <[email protected]> wrote: > > Thanks for the link to the issue, now I can watch it. I have reverted > > to the http work around which I hate due to the lack of security. > > > > On Mar 24, 1:11 pm, Trevor Dean <[email protected]> wrote: > > > > > > > > > > > > > > > > > Yes I was also hoping or a more recent update, the last one was over 18 > > > hours ago and didn't provide much detail ( > http://code.google.com/p/twitter-api/issues/detail?id=2118). > > > > > On Thu, Mar 24, 2011 at 7:56 AM, Ninjamonk <[email protected]> > wrote: > > > > any news on this? bit of a joke that it's been going on for a week > now > > > > and we have no eta on a fix. I have 2 apps waiting to release but as > > > > they feature sign in with twitter I cannot do it. One is for the new > > > > F1 season which kicks off this weekend... > > > > > > On Mar 24, 2:46 am, Craig Walls <[email protected]> wrote: > > > > > No, I'm using the Java-based Spring Social for this. And I've seen > other > > > > > threads describing the same problem with PHP. Definitely not just a > .NET > > > > > problem. > > > > > > > On 3/23/11 6:35 PM, Milos Golubovic wrote: > > > > > > > > I can also confirm this behavior. Is it me or is everyone in > here > > > > > > using .NET? Did I possibly miss somewhere that this is a .NET > forum? > > > > > > I am also using a .NET library (Twitterizer). Wondering if > anyone not > > > > > > using .NET is experiencing this issue? > > > > > > > > On Mar 23, 8:21 am, Craig Walls<[email protected]> wrote: > > > > > >> I've just confirmed what Gary M says...switching to HTTP does > seem to > > > > > >> make it work. But HTTPS requires a>15 second delay between > obtaining > > > > > >> a request token and exchanging it for an access token. > > > > > > > >> On Mar 23, 1:48 am, Gary M<[email protected]> wrote: > > > > > > > >>> Correction. Switching to HTTP does remove the issue, so I'm > making > > > > that a > > > > > >>> configurable setting in our app as a temporary workaround. > > > > > > -- > > > > Twitter developer documentation and resources: > http://dev.twitter.com/doc > > > > API updates via Twitter:http://twitter.com/twitterapi > > > > Issues/Enhancements Tracker: > > > >http://code.google.com/p/twitter-api/issues/list > > > > Change your membership to this group: > > > >http://groups.google.com/group/twitter-development-talk > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
