Forums Scripts & Popups Ban script, with read

Do you really want to ban for ".abc" ? :X

Well, that being said, maybe an ideal script is for the op to set it and forget it...

I was pointing to your 2nd regex that would match a message like
...an efficient method to stop both spam and chat together

Ok how about this:

The main reason I added that is some spammers might say come to blah.com without www. or http://

True. But without any www. OR http:// the OP could simply use one of the many badword scripts arround, And the original request was for a text-based url blacklist.
As I tested my code briefly I suppose he just missed something, e.g. I named the file "forbiddenurls.txt" instead of "urls.txt" to be not mistaken for urls.ini ... likely that I produced confusion by trying to prevent confusion

But does your script kick if I place just .com in urls.txt?

So it *should* work for "*.com" - But that's not what I had in mind
For general wildcard matches I'd use a simple wildcard-badword script. And the read loop above was to keep it simple and .txt-based - $hfind(W|R) would be more efficient.

Ok, I see. Unfortunately it didn't work per your description. I jotted down *.com or *.com* or .com in forbiddenurls.txt
Nothing happened with your script. I understand you didn't consider that function in mind, but wouldn't it be better to adjust it that way to seek .com .net or .org extension?

Erm, it does work, acc. to my description (?)
It doesn't ban for "something.com" but for "www.something.com" or "http://something.com". If you want to ban just for "*.com" you wouldn't need a protocol check at all, and it would be a (lousy) badword script, so why not use a good badword script instead, there are many out there. The downside is that you'd e.g. ban for quoting your $server too.

The script above checks all lines in the textfile against $regml(N)*, where $regml(N) is the text following any occurrence of www/http/https/ftp up to the next space char, that is: a link indicated by a www-host and/or protocol, but without this part, to make matching more versatile.
- If I want to ban "www.google.com" or "http://google.com" or "http://www.google.com", I'd add "google.com"
- If I want to ban all google, I'd add "google." or even "*google"
- If I want to ban "<whatever>.com" I'd add "*.com"

Finally, there are more top-level domains under the sun than *.com *.net and *.org

There are three examples in the initial post, and some more in my last post.
Quoting myself here:

And here:


/me running out of crayons...