| |
Guest EditorialQuestions without Answers Recently, I've participated in an effort to determine the opinion of moderators, as a group, as to how echomail should be handled. Well, I guess I did a little more than participate - I've been identified as ringleader, chief agitator, and a general Enemy of the People :) Don't expect a report of the accords reached real soon - in an ongoing survey with 14 moderators responding, seven have voted against continuing the effort, six have voted for it, and one moderator chose "none of the above." Folks are still voting and the numbers are small right now, so it could go either way - but it's clear that moderators as a group prefer to speak as individuals. Too bad... I'd have liked to see the thinking on the fundamental assumptions which informally govern the movement of echomail. Two assumptions which are so widespread that they're considered axiomatic are these:
The problem is that these principles can be conflicting without some kind of consensus between the moderators and the sysops. A moderator, for example, may determine that a disruptive echo participant should have his posting access restricted, but he is without authority if the participant's sysop won't make the restriction. So what is the consensus? Should the moderator simply accept the fact that some sysops will support him and some won't? Should the moderator seek feed cuts at increasingly higher levels to maintain his authority, knowing that a feed cut beyond the original BBS is likely to cut his echo to many of his other participants? Should the sysop view moderator support as part of his obligation when participating in echomail, and make the restriction regardless of his personal feelings? Should the sysop review each moderator's decision and decide whether to enforce it? Sorry, I don't have answers. I've got opinions, but answers are going to have to come from a consensus of the folks involved. -- |
|