+ User FidoNet address: 1:3634/12.42
> if the gateway looked for the references line,
VG> The gateway need do nothing other than inject your post into
VG> usenet.
the gateway has to format the postings to fit the specification of the
destination network... from this side, that is usenet being the destination...
VG> A post that was properly constructed to begin with - such
VG> as having "Re: " in the subject line of a reply.
my posts are properly constructed... read the RFCs, my friend... they allow for
this...
> how could the software tell from that if i was actually responding
> to the current thread or just using it as a shortcut to starting a
> new thread (bad netiquette) with the same subject or even a new
> thread with a new subject?
VG> My god-damn 12-year-old Netscape Communicator knows to
there is no reason to cuss me is there?
VG> automatically insert "Re: " into the subject line of a post when I
VG> hit reply. Why doesn't your software do that?
because "Re: " is OPTIONAL.. read the RFC... the operative word is "should"...
"should" is not spelled "M U S T"... i also suggest you look at RFC-2119... in
particular, this section...
[quote]
1. MUST This word, or the terms "REQUIRED" or "SHALL", mean that the
definition is an absolute requirement of the specification.
2. MUST NOT This phrase, or the phrase "SHALL NOT", mean that the
definition is an absolute prohibition of the specification.
3. SHOULD This word, or the adjective "RECOMMENDED", mean that there
may exist valid reasons in particular circumstances to ignore a
particular item, but the full implications must be understood and
carefully weighed before choosing a different course.
4. SHOULD NOT This phrase, or the phrase "NOT RECOMMENDED" mean that
there may exist valid reasons in particular circumstances when the
particular behavior is acceptable or even useful, but the full
implications should be understood and the case carefully weighed
before implementing any behavior described with this label.
5. MAY This word, or the adjective "OPTIONAL", mean that an item is
truly optional. One vendor may choose to include the item because a
particular marketplace requires it or because the vendor feels that
it enhances the product while another vendor may omit the same item.
An implementation which does not include a particular option MUST be
prepared to interoperate with another implementation which does
include the option, though perhaps with reduced functionality. In the
same vein an implementation which does include a particular option
MUST be prepared to interoperate with another implementation which
does not include the option (except, of course, for the feature the
option provides.)
[/quote]
VG> Where are your posts being seen - other than on usenet?
uuhhh... Fidonet??
VG> Does fidonet have this exact "alt.comp.anti-virus" group?
you've been told that this group is being gated to fidonet so yes, fidonet has
this exact group... on this side, the echotag for this area is
ALT-COMP-ANTI-VIRUS... what's your point?
VG> Is it against fidonet message-composition rules to pre-pend "Re: "
VG> to the subject lines of replies?
i've been telling you since you brought this up that "Re: " is OPTIONAL in both
networks... do i need to write it slower so you can understand it easier? i'm
not trying to be an ass here... i am, however, trying to educate you about
something that you are apparently ignorant of...
additional, i'm trying understand why you are attacking me all of a sudden...
did you run out of other things to do so you figure you'll stir up some shit
and you chose me as the target?
VG> As for your comment "well my software includes a reference line so
VG> that should tell you it's a reply" -> No usenet client will show
VG> reference lines until or unless you actually bring up the post
VG> itself.
wrong... i have news client software that will show all the header lines
without pulling the message body... the headers are pulled first so they are
available for whatever purposes as desired... the bodies of the messages the
user chooses to read are pulled later when the users selects those messages for
reading or saving to disk...
VG> When displaying the contents of a given group in a linear
VG> view, I'm not aware of any usenet client that will show anything
VG> beyond the subject, author, and date of the post.
i can't help that you are not aware of such... i can't say one way or the other
if i am... it is not something i've gone looking for... it is not something
that i've had a need for, either... i suspect the same actually goes for you as
well...
VG> And why does your software strip away any existing "Re: " in the
VG> subject line when you reply to a reply?
AFAIK it does not but i will check that out especially for you... i will say,
though, that if it is, it is because "Re: " is not required... if it were
absolutely required, then the gateway software would ensure it was there to
meet the specifications... it would do this by detecting the REPLY and/or
References line as i noted before...
[edit] my reader/editor's documentation makes no mention of "Re: " at all...
nothing about adding it to or stripping it from replies... [/edit]
VG> How can you (or anyone else here who is being an appologist for
VG> you) explain that?
no one here is being an apologist for me... obviously you just aren't as
knowledgable as you think you are... i can only try to educate you in those
areas where you are ignorant and i am knowledgable...
VG> It's one thing when your software doesn't add "Re: " when you reply
VG> to the original (first) post of a thread. It's yet something else
VG> when your software *removes* the "Re: " when you reply to replies.
VG> How do you explain that?
"Re: " is not required... since it is not required, it may or may not be added
or stripped... now, let me ask you if it is wrong for a user to manually add or
remove "RE: " from an article's subject line?