On Thu, Sep 3, 2009 at 6:00 AM, PJB 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 storage of Twitter auth
On Thu, Sep 3, 2009 at 5:29 AM, Nicholas Granado 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 criticizing anot
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 ge
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 wrote:
>
>
> $_ =~ s/\-([^\[]+?)\-/process($1)/ges foreach (@tweets);
>
> On Sep 2, 6:50 pm, Dante Soiu wrote:
> > And not computer language, Dante
$_ =~ s/\-([^\[]+?)\-/process($1)/ges foreach (@tweets);
On Sep 2, 6:50 pm, Dante Soiu wrote:
> And not computer language, Dante Soiu
What is it you need help with?
I see more and more of this on the twitter-dev list. On one hand, I
can understand, someone with no developer background, sees the twitter
world happening, and decides they too want to form a business around
it. I do not see this on any of the other mailing
false
On Sep 2, 6:50 pm, Dante Soiu wrote:
> And not computer language, Dante Soiu
