1. Forum
  2. Fidonet
  3. ALT.COMP.OS.WINDOWS-10

  • Change of Subject (was: No CMD)

    From VanguardLH@3:633/280.2 to All on Sun Apr 27 09:50:41 2025
    Keywords: VanguardLH,VLH

    Frank Slootweg <this@ddress.is.invalid> wrote:

    Ed Cryer <ed@somewhere.in.the.uk> wrote:

    VanguardLH wrote:

    Update:

    I did not see your "SOLVED" subthread, because one of my filters
    flags posts that have all uppercase in the Subject.

    It used be standard good netiquette to put "solved" in upper case; in
    Web and Usenet threads. I'm not going to apologise for having done it
    here.

    Well, the "standard good netiquette" was/is to *add* 'SOLVED' in the
    subject line, not to replace the subject. But you're forgiven! :-)

    Netiquette when modifying the Subject header (which adding SOLVED or
    changing to just SOLVED would do) is to show the new Subject header and
    append "(was: <originalSubject>)", so here it looked like:

    Solved (was: No CMD)

    I have also seen:

    Solved - No CMD

    I don't recall "Solved" was to be all uppercased, but I don't visit all newsgroups. Been in Usenet since around 92. At the height of where I
    visited, I used to inhabit 52 newsgroups, but that's waned to 19 now.

    If the original Subject was still there, and "SOLVED" had been added,
    the Subject would not have been all uppercase: the "o" was lowercase. Prepending "Solved" would also not have the Subject as all uppercase.
    I'll look into my all-uppercase filter to see if I can add an exception
    for just "SOLVED"; i.e., Subject starts with "solved" whether upper- or lowercase, or mix of both; however, that would permit starter posts that
    aren't replies, like "SOLVE YOUR DEBT".

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: Usenet Elder (3:633/280.2@fidonet)
  • From Hank Rogers@3:633/280.2 to All on Sun Apr 27 10:13:41 2025
    VanguardLH wrote on 4/26/2025 6:50 PM:
    Frank Slootweg <this@ddress.is.invalid> wrote:

    Ed Cryer <ed@somewhere.in.the.uk> wrote:

    VanguardLH wrote:

    Update:

    I did not see your "SOLVED" subthread, because one of my filters
    flags posts that have all uppercase in the Subject.

    It used be standard good netiquette to put "solved" in upper case; in
    Web and Usenet threads. I'm not going to apologise for having done it
    here.

    Well, the "standard good netiquette" was/is to *add* 'SOLVED' in the
    subject line, not to replace the subject. But you're forgiven! :-)

    Netiquette when modifying the Subject header (which adding SOLVED or
    changing to just SOLVED would do) is to show the new Subject header and append "(was: <originalSubject>)", so here it looked like:

    Solved (was: No CMD)

    I have also seen:

    Solved - No CMD

    I don't recall "Solved" was to be all uppercased, but I don't visit all newsgroups. Been in Usenet since around 92. At the height of where I visited, I used to inhabit 52 newsgroups, but that's waned to 19 now.

    If the original Subject was still there, and "SOLVED" had been added,
    the Subject would not have been all uppercase: the "o" was lowercase. Prepending "Solved" would also not have the Subject as all uppercase.
    I'll look into my all-uppercase filter to see if I can add an exception
    for just "SOLVED"; i.e., Subject starts with "solved" whether upper- or lowercase, or mix of both; however, that would permit starter posts that aren't replies, like "SOLVE YOUR DEBT".


    Here is a forum that might help you and ed.

    https://able2know.org/forum/english_grammar/

    Many experts there that can nitpick the tiniest of grammar mistakes.

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From VanguardLH@3:633/280.2 to All on Sun Apr 27 10:40:41 2025
    Keywords: VanguardLH,VLH

    Hank Rogers <Hank@nospam.invalid> wrote:

    VanguardLH wrote on 4/26/2025 6:50 PM:
    Frank Slootweg <this@ddress.is.invalid> wrote:

    Ed Cryer <ed@somewhere.in.the.uk> wrote:

    VanguardLH wrote:

    Update:

    I did not see your "SOLVED" subthread, because one of my filters
    flags posts that have all uppercase in the Subject.

    It used be standard good netiquette to put "solved" in upper case; in
    Web and Usenet threads. I'm not going to apologise for having done it
    here.

    Well, the "standard good netiquette" was/is to *add* 'SOLVED' in the
    subject line, not to replace the subject. But you're forgiven! :-)

    Netiquette when modifying the Subject header (which adding SOLVED or
    changing to just SOLVED would do) is to show the new Subject header and
    append "(was: <originalSubject>)", so here it looked like:

    Solved (was: No CMD)

    I have also seen:

    Solved - No CMD

    I don't recall "Solved" was to be all uppercased, but I don't visit all
    newsgroups. Been in Usenet since around 92. At the height of where I
    visited, I used to inhabit 52 newsgroups, but that's waned to 19 now.

    If the original Subject was still there, and "SOLVED" had been added,
    the Subject would not have been all uppercase: the "o" was lowercase.
    Prepending "Solved" would also not have the Subject as all uppercase.
    I'll look into my all-uppercase filter to see if I can add an exception
    for just "SOLVED"; i.e., Subject starts with "solved" whether upper- or
    lowercase, or mix of both; however, that would permit starter posts that
    aren't replies, like "SOLVE YOUR DEBT".


    Here is a forum that might help you and ed.

    h**ps:// able2know. org/ forum/ english_grammar/

    Many experts there that can nitpick the tiniest of grammar mistakes.

    The issue is not about grammar. We are discusssing etiquette, not
    grammar.

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: Usenet Elder (3:633/280.2@fidonet)
  • From VanguardLH@3:633/280.2 to All on Sun May 4 00:47:19 2025
    Keywords: VanguardLH,VLH

    Daniel70 <daniel47@eternal-september.org> wrote:

    VanguardLH wrote:

    Netiquette when modifying the Subject header (which adding SOLVED or
    changing to just SOLVED would do) is to show the new Subject header and
    append "(was: <originalSubject>)", so here it looked like:

    Solved (was: No CMD)

    Did you notice how the Subject: changed from your 'Change of Subject
    (was: No CMD)' to my 'Re: Change of Subject' ??

    When modifying the Subject, the "(was:...)" postfix should get added automatically by a proper NNTP client to show the original Subject.

    When replying to an article with the "(was:...)" postfix, the client
    /should/ remove the postfix. It is not necessary nor desirable to keep carrying forward that Subject changed at some point indicating a change
    in topic, or discuss a side topic.

    Notice how "(was:...)" did not get appended when your client added the
    "Re:" prefix. Technically that is a change in Subject, but it used as a qualifier to denote a reply to the same Subject.

    My SeaMonkey Suite (and, I think, Thunderbird) does that auto-
    magically ... getting rid of the bracketed stuff!

    So does mine (40tude Dialog). Proper NNTP clients should.

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: Usenet Elder (3:633/280.2@fidonet)