Text 2718, 50 rader
Skriven 2004-12-05 11:52:56 av mark lewis (1:3634/12)
   Kommentar till text 2192 av Björn Felten (2:203/2)
Ärende: Moderating
==================
 DC>> And scanning 100+ message areas a day accomplishes exactly what?

 BF>    If you made the choice to import 100+ msg areas, you must
 BF> think you will actually read those areas, why else do you
 BF> import them?

for *OTHERS* to use... isn't that what a BBS is for???!!????

 BF>    In the original fidonet days, it worked like this (at least
 BF> in Z2):

 BF>    a) One of the BBS users found out, that there already was
 BF> an echo out there, that handled the issues he was interested
 BF> in.

 BF>    b) The user sent a mail to his sysop, asking him if it was
 BF> possible to get hold of this echo.

 BF>    c) The sysop, being in a temporary good mood, not only
 BF> found the echo but also agreed to import it to the BBS.

 BF>    d) Once the echo was successfully imported, sysop obviously
 BF> appointed above user as 'Meeting ADministrator' aka MAD.

"obviously"???? pure bovine excrement... as long as i've been in fidonet, i've
never heard that term or requirement... i have, however, seen where _some_
systems may do something similar as they may do with haveing a co-sysop that is
responsible for the file areas...

 BF>    e) Hereafter said user was responsible for any outgoing
 BF> traffic from the BBS. Any complaints from other BBSs would go
 BF> to the sysop, and if sysop found out that said user didn't
 BF> perform properly, would immediately cut the feed for that
 BF> echo.

 BF>    I know all of the above sounds really alien to those of you
 BF> in the zone, where one-user nodes are legio, but over here it
 BF> has worked for many, many years. In fact it has worked for so
 BF> many years, we now outnumber you by a ten to one factor. :)

and i have to wonder how truely widespread the methods you describe go... sure,
systems like citadel and such had that built in but other more popular systems
like QBBS, RA and such just do not have that assignment capability built in...
in other words, it is nothing but management style and it appears to almost
even point to the sysop not taking the responsibility but instead passing it
off on someone else...

)\/(ark

 * Origin: (1:3634/12)