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]

sign up to list



On 10/22/2008 11:13 AM, John Abreau wrote:
> On Wed, Oct 22, 2008 at 9:01 AM, Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org> wrote:
>  =20
>> Actually, turning off digest is a  single radio button. I have it turn=
ed off
>> on a couple of low-volume lists. But, some people do find it very usef=
ul as
>> both Allan and Mark mentioned.
>>    =20
>
>
> Nevertheless, turning it off takes away from the people that prefer the=

> digest form, and doesn't provide any benefit to offset that loss. The
> effort to turn it off may be tiny, but it still requires an active deci=
sion
> to do so, which I view as an active decision to needlessly annoy the
> people who prefer digests.
>
> Of course, that logic wouldn't apply to a brand new list when it's
> first being created, nor to a list that had zero digest subscribers.
>
>  =20
Agreed. It depends on the nature of the list. For instance, an=20
announcements only list like the BLU announce list, should probably not=20
have digest subscribers, but most digests are set up to generate a=20
digest when either the size requirement is met, or once a day if=20
non-empty. Digests are certainly a feature that is used on our discuss=20
list as well as many of the other lists we host. The cost of a digest is =

minimal.

--=20
Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org>
Boston Linux and Unix
PGP key id: 537C5846
PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB  CA3B 4607 4319 537C 5846








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