-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 19 Mar 1999 17:44:33 -0500, Ben Pfaff wrote:
>How does reducing CC: traffic to individuals reduce traffic on
>debian-devel? I don't see any direct connection. Sure, sending mail
>*just* to a single developer reduce traffic, but sending mail to the
>list versus the list plus a single developer doesn't make any
>difference at all.
The point is, currently, the list, in general, discourages CCs yet most
people hit reply-to-all and don't trim the CCs out. So what was proposed
was that these same people who don't take the time to trim CCs also now try
to stop and thing "Well, should I take this private?" IE, they hit
reply-to-all and just start hammering away at the keyboard for the reply.
>Currently, people choose `reply' or `group reply' to reply to a single
>developer or the list, respectively. You propose to make everyone
>choose `reply' to reply to the list. How does that help? It just
>makes replying more difficult, and many mailreaders, despite your
>assertions, will default to replying to the entire list anyway.
Correct, it will default but it will *stop* and *ask* where the person
wants the reply to go to. And that is the major difference now. It is that
pause of "Where do you want this reply to go?" Most people want the reply
to go to the list which is why they hit reply-to-all and not trim. But with
reply-to they get prompted and can make a choice. When, honestly, was the
last time when reading a list you didn't reach for reply-to-all out of habit?
>FWIW, I prefer people to CC: me on replies to lists I'm subscribed to.
That's fine and dandy. But your preference is not everyone's preference
and needless CCs do cost people on this list money. For me, I've got a 24/7
connection but I could really do without the added bandwidth usage. On the
whole though, it is better not to CC unless it is requested.
- --
Steve C. Lamb | I'm your priest, I'm your shrink, I'm your
ICQ: 5107343 | main connection to the switchboard of souls.
- -------------------------------+---------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.0 (C) 1997 Pretty Good Privacy, Inc
iQA/AwUBNvLWLHpf7K2LbpnFEQKbLACfYH1Nxsc32bchc5EFf3KalhfFMOoAnils
0G7tUtaDCwIpRXC8nuoEAlxy
=jJeT
-----END PGP SIGNATURE-----