$_ =~ s/\-([^\[]+?)\-/process($1)/ges foreach (@tweets);
On Sep 2, 6:50 pm, Dante Soiu dsoiual...@gmail.com wrote:
And not computer language, Dante Soiu
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
On Thu, Sep 3, 2009 at 5:29 AM, Nicholas Granadongran...@gmail.com wrote:
PJB ... really? There really no need to flame-bait this thread. I think
Scott put it perfectly.
Cheers,
Nick
There was even less need for you to chide him for it. What
contribution did you, a list user, just add by
On Thu, Sep 3, 2009 at 6:00 AM, PJBpjbmancun...@gmail.com wrote:
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
false
On Sep 2, 6:50 pm, Dante Soiu dsoiual...@gmail.com wrote:
And not computer language, Dante Soiu
