Well I must be lucky then. :) I'll probably add redirect support into my library anyway. Shouldn't be too hard to implement.
On Sat, Aug 8, 2009 at 9:25 PM, Chad Etzel <jazzyc...@gmail.com> wrote: > > No, they are not limited to only oauth related calls. > -Chad > > On Sat, Aug 8, 2009 at 10:22 PM, Josh Roesslein<jroessl...@gmail.com> > wrote: > > Are the redirects only occuring with oauth? I've yet to run into them, > but > > I'm not really using oauth much so that might be why. > > > > On Sat, Aug 8, 2009 at 7:09 PM, Howard Siegel <hsie...@gmail.com> wrote: > >> > >> I support them wholeheartedly and appreciate everything they've done to > >> thwart the DDOS attack. > >> > >> While it is true that many of the tools used in the attack do not appear > >> to follow the 302s right now, you can be your bottom dollar that they > will > >> very quickly be updated to do just that, perhaps even quicker than > Twitter > >> can finish recovering from the attack and put in to place measures to > better > >> survive future attacks. > >> > >> At best it is a stopgap to get over the current attack. > >> > >> - h > >> > >> On Sat, Aug 8, 2009 at 16:11, Fawkes <daveha...@gmail.com> wrote: > >>> > >>> They can, but apparently they don't, otherwise Twitter wouldn't have > >>> used it as a tactic. They're going through a very difficult time, we > >>> need to be patient and supportive of them! > >>> > >>> Dave > >>> http://twitter.com/DavidHaber > >>> > >>> On Aug 8, 8:53 am, Kyle Mulka <repalvigla...@yahoo.com> wrote: > >>> > An attacker can just as easily follow a 302 as can a legitimate API > >>> > developer or user of Twitter. I don't understand why Twitter thinks > >>> > this is a solution to the problem. Please stop 302ing. > >>> > > >>> > Thanks, > >>> > > >>> > -- > >>> > Kyle Mulkahttp://twilk.com > >> > > > > > > > > -- > > Josh > > > -- Josh
