Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

TMDA (was Re: best new video cards for linux?)



On Thu, 2003-07-10 at 15:03, Jerry Feldman wrote:

> The list is set up to reply to the poster of the list by default. For
> most listserv software, this is the default out of the box
> configuration. The list owner can easily change that to set the from and
> reply-to back to the list. This is a discussion that has been ongoing
> for as long as we have been running listservs back at the old BCS
> (probably 1992). 
> The intent of the current configuration is that the default reply goes
> back to the poster to reduce list traffic. If one responds and wants to
> respond to the list itself, then edit the To: line. 

The "replyto" issue pops up here periodically, and both sides can 
make plausible arguments in their favor. Someone once suggested 
voting on it, which would probably turn into a Florida tie, and 
we'd likely see repeated calls for votes, resulting in the list 
behavior changing back and forth periodically. 

I felt that inconsistent behavior like that would be far worse than 
any downside from either position, so I essentially made an arbitrary 
one-time decision on it. 

I based my decision on the basis of privacy and failure modes:

* In the absence of a replyto header, something that should have 
  been public might accidentally be sent privately. To recover 
  from the error, the sender can simply resend it. 

* With a replyto header, something that should have been private 
  might accidentally be sent to the public list. To recover from 
  this error, the sender would have to convince hundreds of list 
  recipients to delete the message from their mailboxesd without 
  reading it, and the sender could never be 100% sure that everyone 
  had complied. 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 307 bytes
Desc: This is a digitally signed message part
URL: <http://lists.blu.org/pipermail/discuss/attachments/20030710/1e4e6073/attachment.sig>



BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org