That makes sense. I also think that hackers/spammers can work in teams, setting up accounts that lie dormant for a while until they are exploited.I cannot remember the exact reasons why I chose 100 posts, but it might be due to hackers using old accounts for spamming. Most user accounts have less than 100 posts.
That is exactly what they do, because the dormant user doesn't notice posts that they didn't make.That makes sense. I also think that hackers/spammers can work in teams, setting up accounts that lie dormant for a while until they are exploited.
It's more likely to be bots that they set up rather than actual people sitting there doing the posting.I also think that hackers/spammers can work in teams,
I'm going back a few years for that observation about teams of people. There may have been bots involved, but someone was keeping track of accounts set up for spamming. I suppose once the set up accounts were in place they could then automate the spamming. Gnarly Bastids they are.It's more likely to be bots that they set up rather than actual people sitting there doing the posting.
It would be cleverer if you could whitelist internal links (www.access-programmers.co.uk/...) from the blocker though.
We often ask new posters not to tack on to old threads but start a new one and post a link back to the old one as reference - that gets the generic 'Oops!'
Gnarly Bastids they are.
Probably the ldap that looks like a URLMy previous response has disappeared so let me try one more time. As before, I was entering plain text in a new thread. Here is a copy from my Notepad:View attachment 119247
What in here is deserving of being blocked?
Correct: The use of "://" is there to trap the urls and that would cause the Oops. There is not much we can do about that if we want to stop spammers dropping links.OK, so it seems as if it is purely dependent on finding://
Trying explicitly:
View attachment 119271
results in:
View attachment 119272
Whereas simply doing:
View attachment 119273
is OK:
View attachment 119274
Using a resource but without completing the double forward slash is also OK:
View attachment 119275
The post goes through:
View attachment 119276
Curiously, getting the colon and slashes back to front also triggers the blocker:
View attachment 119277
like so:
View attachment 119278
So, @HavingDatabaseRelations, it really isn't anything personal against you - it's a PITA for everyone!
Here is the admin section that blocks certain phrases. No facilities to whitelist anything. What you see is just part of the phrases targeted.Still not sure why you can't whitelist links back to AWF.
The first line looks like a Regular Expression to me. If this is correct, it should be possible to rewrite the "*//*" line to something that does not match links back to this site but every other occurrence of "//".Here is the admin section that blocks certain phrases. No facilities to whitelist anything.
Shame it takes capitals into account.Here is the admin section that blocks certain phrases. No facilities to whitelist anything. What you see is just part of the phrases targeted.
View attachment 119431
Not sure what relevance that does bear.There is also "//".
Nice find. I ran it through ChatGPT and it suggests it will work, despite the poster on the end of that thread saying it doesn't.Not sure what relevance that does bear.
It appears, it is possible to use RegExps to only reject links to other sites.
Here is a thread in the Xenforo community showing examples: https://xenforo.com/community/threads/spam-phrases-to-detect-external-links-moderate.199113/
Still not sure why you can't whitelist links back to AWF.
Something like this should get you quite far:I don't know if you can do that.
/(([http|ftp|file|mailto|imap|tel|ldap]s?):\/\/(?!(www.)?access-programmers.co.uk)[\w\.\/\-=?#]+)/i