000015d2

REPLYTO: 1:396/3 UUCP

REPLYADDR: me@privacy.invalid
From: Diesel 

"p-0''0-h the cat (UK) - The voice of the Sheeple"

news:ucquj3mxyk40$.n38theo67kmf$.dlg@40tude.net Mon, 16 Feb 2015
02:04:10 GMT in alt.comp.freeware, wrote: 

> On Mon, 16 Feb 2015 01:28:23 +0000 (UTC), Diesel wrote:
> 
>> "p-0''0-h the cat (UK) - The voice of the Sheeple"
>> 
>> news:oy7a70wukkm.avt2wsvs19jq$.dlg@40tude.net Sun, 15 Feb 2015
>> 20:29:48 GMT in alt.comp.anti-virus, wrote: 
>> 
>>> Yeah, that was really too funny. I can't stop laughing.
>> 
>> What's funny is that you failed to identify hex AND base64 coding 
> 
> Hex isn't an encoding scheme. 

Again, I didn't actually use the word encoding or decoding. I know 
you're trying to duck and dodge, but, I wanted to point that out. 
You're actually commenting about something I haven't recently written 
to you. I hate to tell you this, but HEX *can* be referred to an 
'encoding',  in a very loose and I do mean, loose sense of the word.

I'll make an easy example for you. I can use HEX to encode a binary 
file containing high ascii characters into something much more 
usenet/email friendly. plain text. When received, it can be decoded 
back to it's original binary high ascii self; with nothing lost and 
very little chance of damage in transit as it's plain text. It 
wouldn't contain anything that some systems might consider control 
characters. You know all of this though, right? I mean, you have z80 
experience and beyond! You wouldn't say you HEX'd the file and then 
HEX'd it again to convert it back, right?

Wanna play lexicon games with me on this subject again? *smug grin*

> Now we just have to wait until you use encoding and understand that
> hex isn't an encoding scheme and lo you will declare you always said
> so as per your usual MO, and ask everyone to cite MIDs where you
> said any different. 

Hmm. I haven't seen this form of diversion from you previously. I'd do 
well to pay close attention to you. You seem to be trying new things 
as I bring up amusing failures on your end.

I'll make this very simple. I won't even use the word coding this 
time.

You *failed* as in, could not, identify HEX or BASE64. Had you been 
able to do so, you wouldn't necessarily be so quick to try and involve 
FromTheRafters in my commentary concerning your diversion attempt; a 
piss poor one, at that.  

While neither of us referred to any of you posers by actual posting 
nym, we intentionally discussed you right under your noses in a brief 
discussion using BASE64 first and HEX second intentionally to make a 
point. Neither HEX or BASE64 would be considered 'secure' by any 
stretch of the imagination. They were used because they're extremely 
*well known* in the IT world and *should have easily been identified* 
by you and several other posers, script kiddies, and wannabe html 
gurus. The lot of you are *not* what you've been claiming to be and 
this simple demonstration proved that. I didn't even try to trick you 
with an innocent looking but deceptive programming language this time. 
Re: ASIC.

I used something you should have recognized the moment it was visible 
on your screen. You would have been able to see what we were writing 
and I'm certain you would have replied. You respond to nearly all of 
my posts. That one wouldn't have been any different. We both insulted 
you, and, you couldn't see it. Had you been what you claimed to be, 
you would have read our comments with ease.  

> Nice fantasy. Personally I didn't even try to identify whatever you
> are going on about. I have no interest in your silly games. Cite
> the MID where I was invited to play. Not that I read all your word
> walls. 

No fantasy. You can stop pretending you don't read my posts, though. 
We all know you do.
 
>> is certainly something to laugh your ####ing ass off about,
>> though. 
> 
> I doubt anyone in ACF believes you Dustin. 

I'm sure that's very concerning to me. What you personally think.

> Your cred is shot dead. 

*yawn* I really don't care what you think, script kitty. Your opinion 
is as important to me as the #### I took this morning.

> Why don't you just piss off and infect another newsgroup. 

I've been here longer than you. Smug prick.

> We are looking for posters who are both knowledgeable and honest. 

Why are you still here then? You should have been kicked to the 
####ing curb years ago. You aren't exactly what I'd call knowledgable.

> Yunno, with a bit of class. You're just a gobby useless toerag.

So... question above, again.
 



-- 
My truck does not leak. It's just marking its territory! 
--- NewsGate v1.0 gamma 2