I think the UK Telegraph (?) article yesterday put it perfectly... the problem is two-fold: Twitter itself is pretty insecure (unfixed javascript hacks, etc), and third-party apps are even LESS secure (non- encrypted db storage of Twitter authentication on mysql injectable hosts, etc etc).
My general feeling is that Twitter is going to throw baby out with the bathwater in a desperate attempt to shore up its security. This no doubt will mean that the good apps along with the lousy apps will be thrown to the curb (i.e., blacklisted, or whatever). For those of us relying on Twitter app development as something more than just a hobby, or as something more than a chance to speak "computer language", we should really foster a sense of self- regulation that DISCOURAGES the average non-programmer from using Twitter's API. Programming secure, effective, and useful Twitter apps IS VERY HARD. If you don't have expensive programming and db experience, STAY AWAY! This app's NOT for you! On Sep 3, 2:29 am, Nicholas Granado <ngran...@gmail.com> wrote: > PJB ... really? There really no need to flame-bait this thread. I think > Scott put it perfectly. > > Cheers, > Nick > > On Wed, Sep 2, 2009 at 11:37 PM, PJB <pjbmancun...@gmail.com> wrote: > > > $_ =~ s/\-([^\[]+?)\-/process($1)/ges foreach (@tweets); > > > On Sep 2, 6:50 pm, Dante Soiu <dsoiual...@gmail.com> wrote: > > > And not computer language, Dante Soiu > >
