Greetings John!
First I had to TRACK DOWN "(No Subject)" and which technically *IS* a
subject. If it really was NO SUBJECT then there would be
Subject=""
Which still isn't the case. Which is why
Okay man, I got 5:870 messages with "(No Subject) in TBUDL.
That's FIVE out of EIGHTHUNDRED AND SEVENTY MESSAGES! This is not
"Frequent!" This is not a widespread problem!
Out of those FIVE MESSAGES,
Julio Cesar da Costa <jcc@ositedotcomdotbr> Wrote ONE MESSAGE
Nick Andriash <andriash@homedotcom> Wrote TWO MESSAGE
Jamie Dainton <jamie.dainton@lineonedotnet> Wrote ONE MESSAGE
Larry Barrett <larry@kyotecdotcomdotbr> Wrote ONE MESSAGE
That's FOUR PEOPLE OUT OF NINETY EIGHT PEOPLE!!
That's also hardly a frequency worth mentioning.
BTW-I don't see you in there. As of 9-DEC-1999
Anyone want to do further statistics? Like say someone that has 40K
messages in their little database? I know there are people out here
that have 40,000+ messages...
Okay, let's ADD YOU, for a ratio of 5:98 so FIVE PEOPLE
out of NINETY EIGHT PEOPLE, wrote messages with no subject.
5 in 98, Sure is frequent. Wow. Let's round it off to 6/100
6% No Subject
94% With Subject
-=-=-=-=-=-=- Better RE-THINK this FALSE STATEMENT -=-=-=-=-=-=-
"Gaping, gap-toothed presence"
-=-=-=-=-=-=- Better RE-THINK this FALSE STATEMENT -=-=-=-=-=-=-
"Embarrassment?"
You consider, the ability to SEND a message the way you want, without
a nag, embarrassing.
While I consider it a GODSEND not to have restrictive NON-RFC
Compliant nonsense imposed on me.
And RFC 822 shows this:
=== BEGIN
3.1.2. STRUCTURE OF HEADER FIELDS
Once a field has been unfolded, it may be viewed as being com-
posed of a field-name followed by a colon (":"), followed by a
field-body, and terminated by a carriage-return/line-feed.
The field-name must be composed of printable ASCII characters
(i.e., characters that have values between 33. and 126.,
decimal, except colon). The field-body may be composed of any
ASCII characters, except CR or LF. (While CR and/or LF may be
present in the actual text, they are removed by the action of
unfolding the field.)
Certain field-bodies of headers may be interpreted according
to an internal syntax that some systems may wish to parse.
These fields are called "structured fields". Examples
include fields containing dates and addresses. Other fields,
such as "Subject" and "Comments", are regarded simply as
strings of text.
Note: Any field which has a field-body that is defined as
other than simply <text> is to be treated as a struc-
tured field.
Field-names, unstructured field bodies and structured
field bodies each are scanned by their own, independent
"lexical" analyzers.
=== END
Okay, These fields are regarded as "strings of text" it says. Well ""
is *MY* string of text! And there's nothing in the RFC's that say that
shouldn't happen. After all NOTHING *IS* a string.
However if I choose to put something meaningful into that field, to
help YOU SORT through theres nothing wrong with that either, yet if
you REQUIRE ME to have a pop-up NAG SCREEN then your treading on my
shoes.
Your forcing *YOUR TEXT* into the field described by RFC 822/ on *MY*
message, and that my friend don't go down well with homey the clown.
Neither is a Nag-pop-up when it's MY OPTION (as per RFC 822) to leave that
field blank.
Okay, next question, what the hell do you mean by "ordinary users?"
Are you insinuating something here? Nevermind. We won't go there.
I AM Registered /PERSONAL . Ask Stef.
No need to play dirty tricks. The truth will set you free.
READY_
On Monday, May 15, 2000 at 11:51:06 GMT +0900 (which was 7:51 PM where
you think I live) [EMAIL PROTECTED] typed:
JDH> phil <[EMAIL PROTECTED]> wrote:
>>TP> User configurability is the key.
>>Where have I heard that before? Yes, user configurable, right now it
>>*IS* configurable, you type in the subject/or lack of subject, and off
>>you go.
JDH> There are several users of this list who could have been saved the
JDH> embarrassment of sending subject-less messages to the list if a simple
JDH> warning message had been implemented. The existence of these frequent
JDH> subject-less messages, with their gaping, gap-toothed presence in the
JDH> thread tree, points to the need for such a function. It is beyond belief
JDH> that people would oppose such a function. Ordinary users don't oppose it.
JDH> Ritlabs needs to listen to ordinary users, else it will find itself with
JDH> a shrinking piece of a growing pie.
JDH> --
JDH> John De Hoog, Tokyo <[EMAIL PROTECTED]>
JDH> Japanese email software: http://dehoog.org/html/j-email.html
--
... I'm having a ball! With The Bat!
--- The Bat! 1.42f + 98Lite + Revenge of Mozilla II
--
--------------------------------------------------------------
View the TBUDL archive at http://tbudl.thebat.dutaint.com
To send a message to the list moderation team double click here:
<mailto:[EMAIL PROTECTED]>
To Unsubscribe from TBUDL, double click here and send the message:
<mailto:[EMAIL PROTECTED]>
--------------------------------------------------------------
You are subscribed as : [email protected]
