 | | Re: lugnet.announce is not for MOCs
|
|
"William R Ward" <bill@wards.net> wrote in message news:m2advvcf1p.fsf@...rds.net... (...) I agree. I was reading the 'top 1000 noisemakers' thread, one of them referenced back to a post where Todd compiled a list of posters in the .cad groups. It (...) (25 years ago, 3-Jan-02, to lugnet.admin.general)
|
| |
| | Re: lugnet.announce is not for MOCs
|
|
(...) Lugnet has gotten by just fine without moderators, but that's because historically the admin(s) have been there to step in and say "don't do that" and even delete messages if needed. If it is expected that admins will continue to play a less (...) (25 years ago, 3-Jan-02, to lugnet.admin.general)
|
| |
| | Re: Shop At Home catalog Engine Shed
|
|
(...) 1. Don't repost articles to other groups at behest of others (even if they ask nicely). Let them do it. If someone doesn't have posting privileges to some group, it's for a reason, and leave it at that. In lugnet.lego.direct, Jake McKee wrote: (...) (25 years ago, 3-Jan-02, to lugnet.admin.general) !
|
| |
| | Re: lugnet.announce is not for MOCs
|
|
"Todd Lehman" <todd@lugnet.com> wrote in message news:GpDp3A.9B9@lugnet.com... (...) to (...) of (...) on (...) groups (...) .announce. I'm not so sure if I'd want a moderated group, if 'moderation' means 'approved by a live person before getting (...) (25 years ago, 3-Jan-02, to lugnet.admin.general)
|
| |
| | lugnet.announce is not for MOCs
|
|
(...) That's getting pretty bad. Grrrrr. (...) People shouldn't be doing this. lugnet.announce was never intended for announcements of new (especially updates to) MOCs...otherwise the charter would say so. Perhaps it needs to be moderated. The (...) (25 years ago, 3-Jan-02, to lugnet.admin.general)
|
