Slimelite BBS

Re: An political question

Back to FREE25

From Michael Chamberlain · 1996-03-23 03:35 · #73039 in FREE25

In reply to An political question by Pierre Phaneuf

In a message of 09 Mar 96 HECTOR SANTOS wrote to MARK LEWIS:

 HS> You are completely NOT making any sense whatsoever.  Your intepretation
 HS> simply without a DOUBT breaks the addressing sequence which is NORMALLY
 HS> KEEP intact during the normal reply process.  But with "follow up"
 HS> concept, you break the address, WHY?  For what reason?  No, you did it
 HS> all WRONG to begin with and now you are trying to JUSTIFY IT because JAM
 HS> threading was based on this FLAW thinking.

You are completely NOT making any sense whatsoever. Your intepretation simply without a DOUBT breaks the threading sequence which is NORMALLY KEEP intact during the normal reply process. But with "follow up" concept, you break the threading, WHY? For what reason? No, you did it all WRONG to begin with and now you are trying to JUSTIFY IT because SX addressing was based on this FLAW thinking.

Three changes, and you show your own argument to be incorrect. Especially since the MSGID is not intended for addressing of any sort.

 ML>> simply a coincidence... nothing more...

 HS> Coincidence?  It works EACH and EVERY TIME. No coincidence.

OK, then. Think of a series of messages where the MSGID address is a Fidonet address.

If I use the MSGID address as a Fidonet format reply address, it works EACH and EVERY time. Therefore, people who put non-Fidonet addresses in MSGIDs are obviously wrong, because it doesn't work with my implementation. Just ignore the fact that the spec implicitly states that non-Fido addresses are allowed- they don't work with my implementation, so they are wrong.

 HS> Thats whats going in my Documentation.  Users will not buy an argument
 HS> that breaks addressing.

See above. People tried to use the MSGID address in a way it wasn't intended to be used (as a reply address), and some people complained when it didn't work. It doesn't change the fact that the problem was with the use of the MSGID address as a Fido format address, not the non-Fido addresses. Same situation here- it isn't what you want it to be, but that just makes your use of it incorrect, it doesn't make everybody who is adhering to the specification incorrect.

 HS> You guys are doing it all wrong.

The only reason you have offered to "prove" that everybody else in the world is doing it incorrectly and you're doing it correctly is that if people don't do it your way, your software breaks. Not very convincing.

Your justification is that addressing is more important than threading. This is beside the point. The MSGID/REPLY kludges are designed for reply threading, and the REPLY is specified to have the same data as that of the MSGID in the message it is a reply to. Not doing so is breaking the spec. If you don't like it, too bad- the specification is what it is, and it is very unlikely that it will change.

If you really want to "solve" the "problem" (as you perceive it), do it properly. Create a new kludge (maybe TOADDR) for this purpose.

Mike.

--- Spot 1.3a #355
 * Origin: The Point of it all (3:633/265.9)