>> What's the point in proposing another list? If you want to try the
>> experiment, build it. Make it happen.
> Read the proposal. It isn't strictly a separate list. It is a list
> connected by a one-way umbilical cord to the current list. It can't be
> done by just creating another list. It has to be done on the current
> server. Whether the list software is malleable enough to be shaped to the
> task, I do not know. I am leaving it to others to comment on the
> technical issue. The idea is to experiment and create a parallel flood
> channel for certain things that run hot for a couple of weeks but are not
> completely on topic. I don't think this is a "bozo" idea, and I hope you
> will ponder its implications for more than a few minutes.
I belive your idea could still be done on a second server.
For your proposed testrun, a real check about the members
of ClassicCmp to allow access for the sidebar list is not
needed. The listserver will only be made public thru this
list, so any subscription from outside is kind of uncommon.
And even if there are some few, they shouldn't change the
result in a real way. If the idea is right, an add on for
the 'real' server might be made. Or we keep the second and
just exchange the member list every other week to check the
data base and we get another foot to stay on.
Merging both lists into one folder should be no problem for
any mail client out there (also splitting it up again into
several theme folders).
Gruss
Hans
P.S.: No, Steve, no comment on the subject, it's just a
technical response.
--
Ich denke, also bin ich, also gut
HRK
Received on Wed Oct 28 1998 - 14:59:44 GMT