Hmm, using some command line test programs I've developed, I'm still getting 'rel="nofollow"'. For example:
------------------------------ Public timeline 20 statusses Status 0: from HandsomeSmokes, 35229362, Mula Smokes , Brooklyn userImgURLhttp://a3.twimg.com/profile_images/372445265/IMG00064_normal.JPG (en) Wass Poppin Yall..I Go By Handsome Smokes..Im Living Life From A Whole Different Angle..If Needed Hit Me Up Aim - Smokes90z ID 3560548081 created 1 second ago in reply to 3557116376 by 25442179 (Ms_KEN_NSL) with <a href="http://sidekick.com/"; rel="nofollow">Sidekick</a> (en) <a href='prf?u=Ms_KEN_NSL'>@Ms_KEN_NSL</a> BuT Th3 OtH3r OnE iiS ThAt Th3y ZeAdAsS ThiiNk Th3y PoPPiiN WiiTh OuT Us BoYs SaYiiN ShiiT TeW Em 0 URLs -------------------- ... -------------------- Status 12: from petrah, 14461792, Petra Hubbeling, Amsterdam userImgURLhttp://a3.twimg.com/profile_images/341156029/collage2_normal.jpg (nl) Oprichter van Boeddhisness, netwerker op gebied van boeddhisme, marketing, communicatie, sales en recruitment. Bestuurslid Boeddhistische Unie Nederland (en) Founder of Boeddhisness, networker in terms of Buddhism, marketing, communications, sales and recruitment. Netherlands Board Buddhist Union 0.3881578947368421 ID 3560613438 created 2 seconds ago in reply to 3560539429 by 15481144 (LieveLiesje) with <a href="http://www.tweetdeck.com/"; rel="nofollow">TweetDeck</a> (nl) <a href='prf?u=LieveLiesje'>@LieveLiesje</a> Jeemig..... wat ongezellig.... en ik maar denken dat <a href='prf? u=tonvanderhoeve'>@tonvanderhoeve</a> zo romantisch was, heeft hij ze niet eens bij zich? (en) <a href='prf?u=LieveLiesje'>@LieveLiesje</a> Jeemig ..... some unsociable .... <a href='prf?u=tonvanderhoeve'>@tonvanderhoeve</a> and I think it was so romantic, he does not agree with them? 0.5909090909090909 0 URLs -------------------- ... Jim Renkel On Aug 26, 11:09 am, John Adams <j...@twitter.com> wrote: > This was patched yesterday afternoon. > > -j > > On Aug 25, 2009, at 11:38 PM, Costa Rica wrote: > > > > > Hello Twitter, > > Any official word on this apparent vulnerability around the Source > > parameter and cross site scripting? > >http://www.davidnaylor.co.uk/massive-twitter-cross-site-scripting-vul... > > TCI > > > On Aug 22, 9:46 am, Chad Etzel <jazzyc...@gmail.com> wrote: > >> Hi All, > > >> We did not intend for the nofollow string to be included in API > >> results. It is on our list to fix. In the meantime you will need to > >> parse around it. > > >> Thanks, > >> -Chad > > >> On Sat, Aug 22, 2009 at 11:20 AM, Costa > >> Rica<ticoconid...@gmail.com> wrote: > > >>> Thanks to all for your suggestions on how to parse, remove nofollows > >>> or extract the URL, but that's not the bottomline of my message. > >>> There > >>> are some source parameters that are posting automated crap > >>> constantly, > >>> and since I run a trending engine I continuously exclude these > >>> tweets. > >>> Yes I can parse and str replace and even base myself only on the > >>> URL, > >>> but the 2 side effects are that my processing time increase (a > >>> simple > >>> string compare vs a regex) - which becomes significant as I increase > >>> the volume I intend to process, and that the URL's themselves can > >>> easily change to workaround these filters. > >>> I will keep my simple compare - the sites are not that many and the > >>> processing toll of regex'ing this does not merit it - but I would > >>> appreciate some word from Twitter when the source parameter is being > >>> changed, or else some sourceid that is stable. > >>> R > > >>> On Aug 21, 10:17 pm, TCI <ticoconid...@gmail.com> wrote: > >>>> Recently you added nofollow's, and now you moved the nofollow after > >>>> the href. Some of us filter these out and you changing them is only > >>>> making it more complicated. Please make up your mind and stop > >>>> changing > >>>> these... > > >>>> <a href="http://fun140.com/";>Fun140</a> > > >>>> <a rel="nofollow" href="http://fun140.com/";>Fun140</a> > > >>>> <a href="http://fun140.com/"; rel="nofollow">Fun140</a>
