newlogo.jpg

    Help!
    No ops present

      Because the channel is often unsupervised, we have come up with a way to help those who wish to enjoy the channel relatively free from disruption.

      We have had an extra feature in the logos3 bot (since 1999 in Undernet) and the logos9 bot (Since early 2001in Starlink-irc).

      If there are disruptions in the channel, you can message the bot which will alert all Channel Ops who are online, but not in the channel - by a special email.

      If there are ops in channel who are unaware of the situation, logos will message them instead of sending an email.

      It works this way because an op in channel may be watching what is going on, and waiting for a suitable moment to step in and take action.

      If half a dozen other ops come charging in and take over, it may well cause chaos and undermine a bit of ministry that is about to take place.

    How it works

      This is how it works:
      When a disruptive person is causing problems in the channel, a user can type this command in any window on the network:

      /msg logos3 disruption #channel-name

        in undernet
          or
      /msg logos9 disruption #channel-name
        in starlink-irc

        The channel name is important, because both logos bots are in several different channels.

      Upon receiving that message, the logos bot will check to see if anyone it knows as an op is in that particular channel.

      If there is, it will send the ops a message advising them that a disturbance has been reported, and who reported it, and the time the message was sent.

      If there is nobody in channel who it sees as an op, it will instead send an email alert to the full list of Ops. The nick of the person issuing the command will be in the alert. It will NOT do both.

      Any Op who sees the alert in their email in-box can then immediately come to the channel and ask that user what the problem is.

      So if you send the command, please stay in the channel for a reasonable period of time until help arrives.

    Resetting it

      The disruption command can only be sent once without being reset - even if the message was sent to an op in channel instead of the email list.

      This is a safeguard, because the op fixing the problem needs to be aware that he or she has responded to a call for help, and has actually fixed it.

      Only an op can reset logos, so be sure that the situation is such that an Op is definitely needed. And please tell them you have sent a disruption message, because they may have come in without seeing the message.

      When to use the "disruption" command:
      This feature is for emergency situations only... that is, when a lamer is attacking others, using blasphemous or profane language, or causing the entire channel to be disrupted from normal discussion. This includes unnecessary posting of scripture after scripture and !seen after !seen, often with ridiculous or inappropriate nicks.

    When not to use it

      When NOT to use the "disruption" command:
      This feature is not to be used in cases where there is a simple disagreement, or someone is attacking another individual personally. In those cases, just put the attacker on /ignore nick and continue discussion in the channel.

      Please Don't cry "Wolf!"
      If it has been abused by someone sending a "false alarm", that person is prevented from using the command again.

      Here is how it works.
      That person will be devoiced by the bot
      . Not only will they be prevented from sending the disrupt command in the future, but they will also not be able to talk in channel when it is moderated (+m). So, please use the command only when necessary, or face losing the privilege to use it at all.

      We are grateful for your participation in this ministry and hope that this feature in the bot will help make your visits more pleasant.

    Ops' Commands to Reset the "SOS"

      This is how it works:
      Please note that the bot will ignore all commands sent by those who is does not recognise:

      /msg logos3 cleardisruption #channel-name

        in undernet
          or
      /msg logos9 cleardisruption #channel-name
        in starlink-irc

     

    Information Archive
    Chatster.org - Starlink-IRC.org - Undernet.org - Undernet Docs - Undernet attack

    Site Navigation
    Channel History - Channel Policies - Channel Mission - Statement of Faith - Help! no Ops! - Contact us - Stories - Testimonies - Management - General info - Photo album - members' services - WWW access - back to start

     

    last updated on 10th October 2001