This is somewhat orthogonal, but yes: my default plan is to move to
STUMP or something like it. This would allow for several moderators to
share the job, as well as white-listing regular posters. However, the
STUMP requirements are more than the general purpose linux account at
CMU that comp.lang.ml is currently hosted out of provides. So this is
gated by me resolving the hosting situation.
Cheers,
Leaf
Jeffrey M. Vinocur wrote:
> In article
<mailman.1.1206744417.5464.sml-redistribution@[EMAIL PROTECTED]
>,
> Leaf Petersen <sml-list@[EMAIL PROTECTED]
> wrote:
>
>> It is certainly possible to go this route - it would certainly be the
>> easiest for me. :) The major potential issue that I see is that
>> comp.lang.ml and sml-list are tied together, and the volume of spam may
>> be problematic for the readers of sml-list without the moderation
filter
>> in place.
>>
>
> Another option is to employ robo-moderation software that would
> allow known posters through fairly easily, but put some barriers
> in place of spam. This might also allow the work of moderation
> to be shared more easily.
>
> I would suggest STUMP:
>
> http://www.algebra.com/~ichudov/stump/
>
>
> Incidentally, it's probably impossible to get the moderation
> status changed on every server worldwide, so in practice we would
> need some "auto approving" software regardless to deal with posts
> from servers that had not been updated. So we may as well employ
> somewhat more intelligent software to get extra benefits...
>
>
>
|
