diff options
| -rw-r--r-- | .gitignore | 2 | ||||
| -rw-r--r-- | discussion.txt | 0 | ||||
| -rw-r--r-- | outline.rst | 38 |
3 files changed, 39 insertions, 1 deletions
@@ -1 +1 @@ -env/ +env/
\ No newline at end of file diff --git a/discussion.txt b/discussion.txt deleted file mode 100644 index e69de29..0000000 --- a/discussion.txt +++ /dev/null diff --git a/outline.rst b/outline.rst new file mode 100644 index 0000000..b1f8320 --- /dev/null +++ b/outline.rst @@ -0,0 +1,38 @@ +WIP Outline of Commands and Functionality +========================================= + +The permissions are inherited in descending order. Tier 1 inherits Tier 2 ... + +Tier 1 : Administrator/Operator only +------------------------------------ +1. DEFCON +2. SANICK +3. SAJOIN +4. UBAN - Variations. This can be considered akin to a KLINE in tripbot. + + +Tier 2 : Moderators +------------------- +1. NBAN - this will behave as current `nban` minus the kline aspect +2. KBAN - Single channel bans (exists) +3. WARN +4. SUSTATUS + + +Tier 3 : Tripsitters +-------------------- +1. QUIET - should allow for --all flag to quiet accross channels similar to NBAN + 1. This will require the use of the mute extban `MODE +b #channel m:nick!user@host` + 2. Refer to `@kban` and `@iban` code in the `Channel` plugin +2. STATUS +3. ADDNOTE +4. NOTES + + +--- + +- All commands targetting a user (infractions) should be logged in a database. sqlite3 for now. + - decide upon the schema for these tables. +- Besides the user permissions, there should be channel restrictions for certain commands. +- Ensure that the bot itself cannot be targetted and is immune + |