Subject | Re: Flint is running away as fast as he can! |
From | Sandman |
Date | 03/14/2013 19:16 (03/14/2013 19:16) |
Message-ID | <mr-B8D714.19165614032013@News.Individual.NET> |
Client | |
Newsgroups | comp.sys.mac.advocacy |
Follows | Flint |
Haha! Your inability to read English is becoming worse, it seems.FlintFlintSandman
Sandy also fails to mention there IS NO RFC for software to handle message-IDs IN THE BODY of MESSAGE TEXT, only in >message headers<
Incorrect, there is no RFC that says how a client should "handle" a Message-ID in the message headers, Einstein.
Damn there's an echo in here. I believe that is just what I said, IDIOT.
Hahahahahaha!!!!! That's actually what you really think! This is so unbelievably funny.SandmanFlint
I don't care that your lousy software can't handle Message-ID information that is relevant to the medium in which it operates - I am making fun of the fact that you had NO IDEA that it was a Message-ID and thought it was a *BROKEN EMAIL ADDRESS*
I didn't just 'think' it was, it IS a malformed email link because that's what posting into the body of text makes it become.
Now, one can preserve the message ID text string format while actually making it a HTTP link straight to a google groups arcive of the intended message.It's *NOT* a HTTP link, it's a NNTP resource URI, monkey boy! What is it with Windows fanboy idiots that can't handle anything but HTTP links. If I would have wanted to point to a HTTP resource, I would. I wanted to correctly point to a NNTP resource. And did. Successfully.
You failed to do that however. I was making fun of your half assed lazy attempt to provide a useful cite by playing with you over what ended up amounting to a broken email link.Hahahahahahahhahhahahhahahhahahahh!!!!!!!!!!!!!!!!!!!!!!!!