R
Richard Choate
I knew when this first got posted that it would be like similar posts I've
seen regarding behavior of users instead of just solving Excel problems (or
Access or Word, etc). I knew then that this thread would be like cancer and
just keep getting bigger and bigger. At least it isn't so nasty any more. I
think I better just delete the thread now.
R Choate
Yes, this is a brand new thread inspired by other threads, specifically,
http://www.google.com/groups?threadm=#[email protected]
bl&rnum=1&prev=/groups%3Fdq%3D%26hl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%2
6selm%3D%2523Ss59VHUDHA.2196%2540TK2MSFTNGP12.phx.gbl
(or http://makeashorterlink.com/?W28165465 )
and
http://www.google.com/groups?threadm=jemcgimpsey-7F716B.22382512072003@msn
ews.microsoft.com&rnum=1&prev=/groups%3Fhl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3D
UTF-8%26selm%3Djemcgimpsey-7F716B.22382512072003%2540msnews.microsoft.com
(or http://makeashorterlink.com/?L2C115465 ).
So, what's the verdict?
Is crossposting the evil twin of the devil's spawn, multiposting?
Do we have to refine what we mean by 'fractured thread'?
And why not a few comments while I'm at it?
- If Google Groups is 'storing' posted articles in a single newsgroup - the
first that appears in the Newsgroups tag - no big deal. It's efficient and
VERY
sensible for an NNTP server to store any given message ONLY ONCE. If the
server
accomodates multigigabyte daily throughput, minimizing article storage and
transmission with other NNTP servers is an absolute necessity. As long as
those
articles 'appear' in listings of other crossposted newsgroups, who cares how
they're stored on the server?
- Responding to a crossposted article in FEWER newsgroups without using
Followup-To tags is, in a practical sense, worse than multiposting
(converting
originally crossposted threads to an effectively multiposted ones -
respondents
should know better than OPs). If we're going to gripe about multiposting, we
should come down even harder on people who fracture threads by doing this,
whether they do so out of ignorance or conscious though misguided belief
that
they're 'fixing' crossposting - by converting it to multiposting!
- There are some newsreaders that can't handle crossposting. The only one
I've
used myself is AOL's. To use AOL's, it's necessary that AOL be ISP, but if
so,
all versions of AOL's software since version 4 (both 16- and 32-bit
versions)
allow Outlook Express to run at the same time, so AOL users using version 4
or
later *could* use OE as their newsreader rather than relying on AOL's.
- CDO allows crossposting, but it doesn't mark crossposted articles as read
in
all crossposted newsgroups when read in any one of the crossposted
newsgroups.
However, if you close your browser, then reload it and go back to the *same*
newsgroup in CDO, you'll find that it doesn't retain *any* 'previously read'
indicators. Add that to its stupid sort order which leads so many to repost,
and
it's sad but true that CDO users have a crippled newsgroup experience
ignoring
the crossposting issue. Indeed, if you crosspost to .misc and .links, it'd
be
much easier to find responses in .links made by people reading and
responding in
misc - crossposting to high *AND* low volume newsgroups may actually
*REDUCE*
the instances of CDO reposting - a good thing!
seen regarding behavior of users instead of just solving Excel problems (or
Access or Word, etc). I knew then that this thread would be like cancer and
just keep getting bigger and bigger. At least it isn't so nasty any more. I
think I better just delete the thread now.
R Choate
Yes, this is a brand new thread inspired by other threads, specifically,
http://www.google.com/groups?threadm=#[email protected]
bl&rnum=1&prev=/groups%3Fdq%3D%26hl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%2
6selm%3D%2523Ss59VHUDHA.2196%2540TK2MSFTNGP12.phx.gbl
(or http://makeashorterlink.com/?W28165465 )
and
http://www.google.com/groups?threadm=jemcgimpsey-7F716B.22382512072003@msn
ews.microsoft.com&rnum=1&prev=/groups%3Fhl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3D
UTF-8%26selm%3Djemcgimpsey-7F716B.22382512072003%2540msnews.microsoft.com
(or http://makeashorterlink.com/?L2C115465 ).
So, what's the verdict?
Is crossposting the evil twin of the devil's spawn, multiposting?
Do we have to refine what we mean by 'fractured thread'?
And why not a few comments while I'm at it?
- If Google Groups is 'storing' posted articles in a single newsgroup - the
first that appears in the Newsgroups tag - no big deal. It's efficient and
VERY
sensible for an NNTP server to store any given message ONLY ONCE. If the
server
accomodates multigigabyte daily throughput, minimizing article storage and
transmission with other NNTP servers is an absolute necessity. As long as
those
articles 'appear' in listings of other crossposted newsgroups, who cares how
they're stored on the server?
- Responding to a crossposted article in FEWER newsgroups without using
Followup-To tags is, in a practical sense, worse than multiposting
(converting
originally crossposted threads to an effectively multiposted ones -
respondents
should know better than OPs). If we're going to gripe about multiposting, we
should come down even harder on people who fracture threads by doing this,
whether they do so out of ignorance or conscious though misguided belief
that
they're 'fixing' crossposting - by converting it to multiposting!
- There are some newsreaders that can't handle crossposting. The only one
I've
used myself is AOL's. To use AOL's, it's necessary that AOL be ISP, but if
so,
all versions of AOL's software since version 4 (both 16- and 32-bit
versions)
allow Outlook Express to run at the same time, so AOL users using version 4
or
later *could* use OE as their newsreader rather than relying on AOL's.
- CDO allows crossposting, but it doesn't mark crossposted articles as read
in
all crossposted newsgroups when read in any one of the crossposted
newsgroups.
However, if you close your browser, then reload it and go back to the *same*
newsgroup in CDO, you'll find that it doesn't retain *any* 'previously read'
indicators. Add that to its stupid sort order which leads so many to repost,
and
it's sad but true that CDO users have a crippled newsgroup experience
ignoring
the crossposting issue. Indeed, if you crosspost to .misc and .links, it'd
be
much easier to find responses in .links made by people reading and
responding in
misc - crossposting to high *AND* low volume newsgroups may actually
*REDUCE*
the instances of CDO reposting - a good thing!