Slimelite BBS

An political question

Back to FREE25

From HECTOR SANTOS · 1996-04-05 07:40 · #73064 in FREE25

In reply to An political question by Pierre Phaneuf

HS>> But its only becomes UNGUARANTEED during the rare "follow up"
HS>> situation.

PP> And how to you recognise such a message from ordinary replies? If you
PP> find such a algorithm, I agree we could use the REPLY address for
PP> addressing, since we'd know when it would be right or not.

Your thinking or mind set is that its "wrong".  99% of the time it is
not. I don't think "recognition" has anything to do with it.  We are
talking natural algorythms.  Where you have "ADDRESSING" available. I
will go with the natural presumption that they are "always" right.

Now that I am aware that it MAY NOT be right because of "follow ups",
the best one can do at this juncture is just make a "NOTE" of it to
the end user, either with a PROMPT or whatever.

If the editor package has a NODELIST for lookup, then its a mute point
and I think that a major reason why here we have a different point of
view of it - most people here are sysops, have a BBS or point system and
have a NODELIST available.  But I can assure you that END-USERS, the
majority of your email writers do not have access to a nodelist to do
verification.

What I am basically saying that with FTS-9, we have the OPPORTUNITY more
than EVER before to correct or OFFER one of the MOST important aspects
of electronic mail communications, and that is proper addressing.

PP> In fact, when I'll see Joho gets into this, I think I'll stop adding
PP> to this thread, since I'll only have to lay back and watch...

Joho is one of the gifted young engineers and he has shown that threw
his technical writings more so than his software.  He is one that likes
to see the "entire picture".  In my opinion, I would think he would
agree with me but would submit to the current ill usage of FTS-9 because
its now one of those things where its too late.  It does effect the
threading algorytms of many mail processors out there.

So the reason question, is there a compromise were we can keep the
integrity and important of addressing in the mail while still have
threading?

PP>>> Answer this question: Is FTS-9 more for message reply linking
PP>>> or addressing?

HS>> Without a doubt, uncategorically, undenyably, ADDRESSING is more
HS>> information and have more practice use for MOST applications and users
HS>> than threading.

PP> You missed to question. I was not asking which is more important, I
PP> was asking what FTS-9 has been made for.

I say its for BOTH. MESSAGE IDENTIFICATION to me implys the ABILITY to
"identify who" wrote the message and REPLY LINKING implys to me the
ability to MAP the "HISTORY" of the thread.  Its BOTH and it works 100%
perfectly for your more NATURAL reply system.  It breaks for a FOLLOW UP
and thats only because software writers literally took the statement in
FTS-9 to use the current MSGID for your reply as their "natural" reply
engine in their software.  What was not clarified or "considered" was
the "follow situation".

PP> Ask any Usenet zealot about the importance of threading, and
PP> considering the> mass of mail they have to wade through these days,
PP> an avid Usenet users is a user to listen to for features they'd like.

In my OPINION, this is a perfect example of where ADDRESSING is just as
important.  How many times has you read a REPLY and its to ALL. You
don't know who he is REPLYING too.  So yes, you are STUCK to use a
THREADING system to find out.  But this only WORKS for the small amount
of people, like sysops, who HAVE access the entire or lenghty database
of mail.  Most people do not.  So its just as important to keep an
"reply system" to BOTH parties in the CURRENT message.   Thats just
common sense to me.

HS>> Where does it say in FTS-9 that addressing is not important? Where
HS>> does it say that REPLY does not POINT to a PERSON?  Many authors and
HS>> people in the industry will equate a PERSON to a ADDRESS.  Who are you
HS>> talking to? Ether?

PP> Must point to the MSGID of the message to which this message is a
PP> reply. Excerpt from FTS-9......

You see thats the point, you took "academic theory" and neglected
"practical implementations" due to inexperience.  You didn't extrapolate
for additional scenarios.  In you had a product in practice, you would
followed FTS-9 and saw that in your natural reply system, the ADDRESSING
was always correct and the threading was intact.  Perfect!!! right?  Then
in a future version of your software because someone ask for it, you
added a "FOLLOW UP" and now you see that the "ADDRESSING is no longer
correct".  "Hold a minute!", you said as an engineer.  How do I solve
this problem?

You say "Addressing was ALWAYS correct in the normal reply system". Let
me go back to FTS-9 "hmmmmm, it doesn't say that ADDRESSING is not
important and this is among the first most important specs that
addresses the need of identifying individuals/sites by address...hmmm?"

You sit down and analyze your natural REPLY engine logic and draw a
truth table with the BASIC assertion that ADDRESSING must stay intact
and you will conclude that ADDRESS is important and that isn't be
broken just so we can keep the same "serial no" for threading.

PP> Yes, but the threading kludge point to the message that is being
PP> replied to.

But you sent me a NETMAIL now, where does the THREAD come into play? How
would your EDITOR now back track to find the original message based on a
THREAD that originated in a different FORUM?

PP> When I use the reply to other person feature, I'm still
PP> replying, and that's why it's correct to have REPLY address different
PP> than the address of the person I'm writing to. I want it to point to
PP> the message I was reading when I pressed the key to reply.

So what if you want to repl a message to me via netmail? You see Paul
write a message to me, and you want to instantly reply to ME via netmail
using the same message?  It may work for you with your sysop editor
having a nodelist, but for the majority of the end-users, you deny them
the right to use that feature and technically, there was NO reason for
it.  ALl I am hearing is that it will break the "SYSOPS" threading logic
on his local machine.
--- Platinum Xpress/386/Wildcat! v1.2j
 * Origin: Xpress Tech Support BBS * 305-248-7815 (1:135/382)