From b86e4aa78f8d3f7a678ad9a743bf477d5f937652 Mon Sep 17 00:00:00 2001 From: djmcgrath Date: Mon, 22 Oct 2007 15:02:44 +0000 Subject: [PATCH] * New doc/ directory * Moved USAGE to doc/ * New pod formatted manual for infobot.users git-svn-id: https://svn.code.sf.net/p/infobot/code/trunk@1592 c11ca15a-4712-0410-83d8-924469b57eb5 --- USAGE => doc/USAGE | 0 doc/infobot.users.pod | 158 ++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 158 insertions(+) rename USAGE => doc/USAGE (100%) create mode 100644 doc/infobot.users.pod diff --git a/USAGE b/doc/USAGE similarity index 100% rename from USAGE rename to doc/USAGE diff --git a/doc/infobot.users.pod b/doc/infobot.users.pod new file mode 100644 index 0000000..264196a --- /dev/null +++ b/doc/infobot.users.pod @@ -0,0 +1,158 @@ +=pod + +=head1 NAME + +infobot.users - User accounts database for infobot + +=head1 SYNOPSIS + + # Please edit to your needs. + # "local" is used for CLI mode + # Passwords can be generated with mkpasswd in linux + + _default + --FLAGS amrt + --HOSTS *!*@* + + local + --FLAGS Aemnorst + --HOSTS local!local@local + --PASS xxfxfIfoJHdYg + + timriker + --FLAGS Aemnorst + --HOSTS *!~timr@TimRiker.active.supporter.pdpc + --PASS xxfxfIfoJHdYg + + xk + --FLAGS emnorst + --HOSTS *!xk@example.com + --HOSTS *!xk@superbox.home.org + --PASS 5K/rmJPzwxJhU + +=head1 DESCRIPTION + +This file controls who has access to use your infobot. + +=head1 FIELDS + +There are various fields allowed in your file. Whitespace is ignored, and as +usual, any line starting with a C<#> is treated as a comment. + +The first non whitespace/comment line in your file, is the user name for the +account you are about to define. Take note that a special username called +C<_default>, is meant to define what everyone who doesnt have an account in this +file should use for permissions. + +Also, the special user name C, is used when you run the bot in B +mode (console only, no B connection). As well, the C user requires a +special hostmask of S>. + +Below is a list of the valid options available for each user account. + +=over + +=item B<--FLAGS> + +This field is a list of possible flags that this account has. Think of them as +similar to irc user modes (although, with different meanings). + +Here is a list of the current flags available, and their meanings: + +I + +=over + +=item * + +B - bot administration over /msg (default is only via DCC CHAT) + +=item * + +B - dynamic ops (as on channel). (automatic +o) + +=item * + +B - add topics. + +=item * + +B - ask/request factoid. + +=item * + +B - modify factoid. (includes renaming) + +=item * + +B - bot owner, can "reload" + +=item * + +B - master of bot (automatic +amrt). + +=over + +=item * + +Can search on factoid strings shorter than 2 chars + +=item * + +Can tell bot to join new channels + +=item * + +Can [un]lock factoids + +=back + +=item * + +B - remove factoid. + +=item * + +B - teach/add factoid. + +=item * + +B - Bypass +silent on channels + +=back + +=item B<--HOSTS> + +This field is used to specify a hostmask that a user must appear from for the +bot to consider them to be this specific account definition. + +This hostmask takes the form of: I + +I + +=item B<--PASS> + +This field used a C formated password, that is used for B chats to +the bot, or if you need to identify yourself to the bot in the event that you +come from a different host. + +You can generate one using the C command, available on most systems. + +For example: + + infobot@myhost:~$ mkpasswd + Password: test + GVrl9PMBB0gpw + +You can also change your password at anytime by sending the bot a C +command on B. + +=back + +=head1 BUGS + +At some point, it is likely that the C account will be removed and +implied to have full access. + +=cut + -- 2.39.2