Subj : Re: Fwd: Girls got chip planted without them knowing it
To   : kk4qbn
From : Gamgee
Date : Fri May 17 2024 07:49:00

-=> kk4qbn wrote to Wilfred van Velzen <=-

 kk>   Re: Re: Fwd: Girls got chip planted without them knowing it
 kk>   By: Wilfred van Velzen to MRO on Fri May 17 2024 09:27:09

 MR>> do you not know how to twitfilter?

 WV> Of course I do. But that is not fixing the problem. And it's just a
 WV> temporary "fix" until they log in with a different name...

 kk> Really, all it boils down to is the Sysops AND the EC,
 kk> Moderators, or whatever title the person who provides the mail to
 kk> the sysops not running the networks correctly..

You don't have a good understanding of how modern echomail distribution 
happens.

 kk> 1. If the EC, Moderato, or whatever title of the day detects a
 kk> message they do    not see fit, they need to delete it before it
 kk> goes further downsteam and    notify the offending systems sysop
 kk> so it can be remedied.

When messages arrive at a hub, they are sent out to that hub's downlinks 
in a matter of seconds.  Yes, seconds.  There is ZERO chance that the NC 
(the correct "title") is going to catch/stop an offending message.  
ZERO.  They come in, and immediately go back out to downlinks.  Even if 
the RC/NC was sitting at the computer with his hands on the keyboard, 
they could not stop the message from going downstream.

 kk> 2. This EC, Moderator, title of the day, or whatever they call
 kk> themselves need
 kk>    to login and check on their message bases more than once a
 kk> week, should
 kk>    really be daily.. some of these people you cannot even get
 kk> ahold of..
 kk>    if they cannot do this, something needs to be remedied to
 kk> replace them.
 kk>    if that is'nt an option, then the network should be considered
 kk> obsolete.

LOL ... While some of the above is certainly true, "checking on their 
message bases" would have nothing to do with catching/stopping an 
offensive message.  It can't be done.

 kk> 3. The ^^ above mentioned person needs to arrange that every
 kk> Sysop check in    once weekly in the Sysop area so that everyone
 kk> can keep on point, If they
 kk>    miss a check-in and/or a couple follow up messages they should
 kk> be put on
 kk>    hold until they pay attention..

Even bigger LOL!  That's not gonna happen.  Unfortunately, there are 
indeed quite a few sysops/systems that are on "autopilot", and that is 
very difficult to resolve.  Probably not possible any more.

 kk> Heck.. thats really about it.. It's not a "Dumb" sysop issue,
 kk> It's a "Lazy" sysop issue. and the main issues is with some of
 kk> the upstream hubs, etc who do not correctly maintain their
 kk> message networks. whether it be an FTN, QWK, etc.

See my first sentence above about not understanding how message 
distribution works.  You're not even close.

 kk> A simple structure should be laid out by that EC, and explained
 kk> to every Sysop that gets a feed from that EC.

Easy to say; impossible to put into actual practice.


.... All hope abandon, ye who enter messages here.
--- MultiMail/Linux v0.52
 þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.