ub
 Share
 
View only
 
 
ABCDEFGHIJKLMNOPQRS
1
Originally eir was introduced in the #ubuntu channel because of bug #521842 (Add feature to prevent setting and forgetting bans/quiets) Since eir is still not set to (by default) auto-remove-after-expire, and there are several bugs filed without any solution in the forseeable future, that experiment failed.
2
3
4
Issues filed against eirRequirements replacement botMoSCoW
5
6
feature to prevent forgetting bans/quietsremove expired bans/mutes without intervention of an OPM
7
eir is not in other #%ubuntu% channelssingle solution fit for all (core?) channelsS
8
eir is not in sync with BT (currently workaround)full sync with bantrackerS
9
eir floods teamchannel (moved to -ops monitor)capability to remind in pm as well as in -ops-monitorC
10
any input in /query with eir is interpreted as commentnot accept incorrect syntaxS
11
eir and the floodbots don't get on with each othercause no conflicts with existing bot(s)S
12
eir config settings not optimal (operates in batchmode)capability to differentiate between a nag and action batchC
13
would be nice to set multiple ban expiry rules in one commandcapability to edit multiple bans/mutes in single commandC
14
would be nice to see if ban is set to auto-remove or notcapability to show ban/mute status including action at expiryC
15
eir should complain at incorrect syntaxnot accept incorrect syntaxC
16
24x7x365 availabilityM
17
single channel maintanance bot (besides floodbots?)?
18
capability to report similar bansW
19
require a comment for each ban/mute (maybe in nag?)C
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...
 
 
 
Sheet1