View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001529 | unreal | ircd | public | 2004-02-09 21:37 | 2004-02-19 23:42 |
| Reporter | LoVeR | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | open | ||
| Summary | 0001529: Anti Spam ideas | ||||
| Description | Hello... We are (9 ppl) thinking of how to get rid of adv/spam messages... 1- /badword message (IRCop or Serveradmin command) command that will understand even colored messages. Yes, you said lots of times we have to use regexp at badwords.conf but few ppl really knows exactly to use regexp. By this command any colored/bold etc message can be added to badwords.conf. Maybe it is hard to code it but it is an idea. 2- Excess flood Glining with a line at conf. 3- Away Messages censoring. (like badwords away) 4- user who enter channel #spammer cant join #channel like mode. (/mode #channel +mode #spammer) | ||||
| Additional Information | Just Ideas to get Unreal work better against spammers. | ||||
| 3rd party modules | |||||
|
|
5- Zlineing after for example 20 times trying to use q:line nick. |
|
|
Some of what you said is already done for the next version :) We added a new command /spamfilter along with spamfilter {} blocks to the config file. These use regexp however. If you don't know regexp however, that's not our fault and we're not going to waste our time making it have an "idiot proof version." If you want to use it, then learn regexp. Also we added an "extended ban" system. One of the new extended ban types is a "channel ban" you'd do: /mode #channel +b ~c:#spammer Then if the user is in #spammer they cannot join #channel. |
|
|
Of course we want to use it and using it. This kind of "idiot proof version" things make Unreal used by more servers. Think that you added Regexp, maybe worked a lot about it but people arent using it. Is it better or worse? Thanks for the info... |
|
|
Here's the thing you neglect though. If we were to also add a non-regex version we've just made unreal slower, and potentially buggier. Why should we do that? Admins should not be stupid imho. If they don't know how to do something then they should learn, they shouldn't look for someone to do it for them. If that's the way someone runs their server, then imho they are doomed to failure. |
|
|
I totally agree, UnrealIRCd is always ment to be an advanced ircd... regex is not hard to learn at all and should be well within the "brain limits" of admins, in fact when you want to match on certain phrases/words without any wildcards and stuff, that works quite reasonably well even if you don't know regex, like "come watch me at" or "go to www.blah.com" [1], "DaAdvertisingNet" etc... And last but not least: it's good for them to invest some time in learning regex, this will considerably help them in fighting those bots/worms/etc because it can be very powerful. [1] sure the dot will match any character but there's like 0.01% it will ever give a false positive, and again: just learn a bit on regex and you know! There'll probably be an regex section added in the docs too to make it even easier. |
|
|
I think we can close this. 1. seems pretty much in spamfilter now (and no intentions to add /badword cmd) 2. bad idea, an evil guy could just make someone excess flood (ctcp flood for example) and (s)he is dead for X hours thanks to the *line.. great. 3. don't understand why that would be useful.. you only see the away reason if you /whois someone or msg him/her. 4. +b ~c:#chan now |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2004-02-09 21:37 | LoVeR | New Issue | |
| 2004-02-09 21:40 | LoVeR | Note Added: 0004924 | |
| 2004-02-09 21:54 |
|
Note Added: 0004928 | |
| 2004-02-09 22:28 | LoVeR | Note Added: 0004929 | |
| 2004-02-09 22:49 |
|
Note Added: 0004930 | |
| 2004-02-09 23:31 | syzop | Note Added: 0004932 | |
| 2004-02-19 23:42 | syzop | Status | new => closed |
| 2004-02-19 23:42 | syzop | Note Added: 0005100 |
