🚀 go-pugleaf

"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message 
news:9LydnTmix6vPviDXnZ2dnUVZ_rudnZ2d@giganews.com...
> From: "FromTheRafters" <Erratic @nomail.afraid.org>
>
>
> | "The Real Truth MVP" <trt@void.com> wrote in message
> | news:He-dnfL92cznsyHXnZ2dnUVZ_uadnZ2d@giganews.com...
>>>I explained that file a whole year before you trolls found it. I posted
>>>about it in my blog using the very same code used in the file and I told
>>>you all that when you thought you "found" something. But of course you
>>>trolls always "pretend" you missed that post.
>
> | Oh yeah, that was the funniest part of your acting the fool.
>
> | (I know ... I know ... it's not an act)
>
> | To think that anyone would believe that an actual malware file (not just 
> a
> | marker) had been named with a ROT-1 encoded "pcbuttsthief", and that it
> | appeared in your version prior to it appearing in "roguefix", is 
> ludicrous.
>
> | One thing is that many of us knew in advance that the marker was there 
> in
> | "roguefix" and only later on did it appear in your "remove-it". The
> | direction of flow of information (from roguefix to remove-it) is
> | irrefutable - and yet you keep trying. The only person that would 
> believe
> | such a thing as you propose is ... well ... only *you* would believe 
> such
> | idiocy. Nothing that you can propose about the existence of
> | "obatssrsghde.exe" can negate the fact that information flowed from the 
> real
> | author to you and not the reverse.
>
> | ...but by all means, do keep trying - I make more popcorn. :oD
>
>
> Add a few drops of, non blended, dark sesame seed oil to that popping corn 
> when you make
> it.  It gives it a bit nuttier flavour.

Hmmm, that sounds good, but in view of the type of entertainment - that 
would make everything a bit *too* nutty. :oD

[...]