On Sunday, Nov 23, 2003, at 16:24 US/Pacific, R. Joseph Newton wrote: [..]

[blush] ...uh, and make sure your'e looking at the headers for the right
post. [/blush]


Joseph

dude, we all have those little decaf moments.... trust me on that.... 8-)

It is possible that you can 'deja news' the article,
from one of those grand religious holy wars about which
header whatNotStuff was required, should be required,
would be really cool if they were required. To make the
point that things Might be getting out of hand the
person posted up what would turn out to be something
like 60-120 lines of 'header' for the 'one liner'

don't you think this is getting out of hand?

which we all laugh at as we look back fondly on that,
but given that we are still running way long, there
was something like 36 lines of header for 27 lines of
message - and that was for a Flat Text Email, vice the
multi-parters where there is a flat text version, and
one version that is html-ish, and one version that is....

{ so that we can keep this in perspective, the response
I just got from Jason, rolls some 108 lines of foo so that
I can read 44 lines of text with or without fancy formatting.
and then there is the Header Section on top of that.}

As some folks run into, on a semi-regular basis, someone will
ship out an email message that came from an MS client that
is nicely 64bit encoded, but also unreadable on various
email clients that simply dish up the 'text' with all of
those headers. Hence folks see these really nice non-sensical
pretty packed blocks of 64bit encoded stuff that is not
human readable.

So while I can empathise with the desire to have nicely
threaded stuff, there may be more important issues that
really need to be addressed than merely attempting to
advance the cause of software friendly header foo for
email/nntp/http information interchange.

ciao
drieux

---


-- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to