Absolutely! Or communities founded for short-range use by a few people that aren't *intended* to stay in use long enough for mods dropping out to be a problem.
I think a good compromise would be to have a place on the community creation page for a backup maintainer if the creator of the community so desires, explaining why it might be a good idea, but not *requiring* it. The idea of triggering a warning/notice to the community if the maintaner hasn't shown up on the service for an extended period of time might be a good idea too, but I'm no programmer and I have a sneaking suspicion a thing like that might either open itself up to abuse or cause greater excuse to kvetch when theings invariably go wrong for some community in the future--wouldn't DW be opening up some responsibility for making sure a com has an active maintainer, in that case? Which is not something they can realistically do, without getting *way* more heavy-handed than anyone wants, especially them. Beatrice Otter > I'm not sure that requiring the appointment of a 2IC is the best idea - > many > people on LJ, for example, create a closed community solely to post their > icons, fiction, art, etc. and the community is never intended to be used > by > more than one person. In this case, appointing a second-in-command rather > defeats the purpose. > > Lassarina Aoibhell > Webmaster, The RPG Place > http://www.rpgplace.net _______________________________________________ dw-discuss mailing list [email protected] http://lists.dwscoalition.org/cgi-bin/mailman/listinfo/dw-discuss
