Feature #1726
Spam Ninja Updates
| Status: | Closed | Start date: | 09/14/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | Tom Moore | % Done: | 100% |
|
| Category: | Other | |||
| Target version: | 1.6.5 |
Description
In addition to the Spam Ninja plugin and as per an internal discussion, the following features will be added:
- Birthdays
- New usergroup setting - display users in the birthday list
- New general setting - only show users with more than x posts in the birthday list
- Signature Control
- New usergroup setting - can add signature
- New usergroup setting - can add signature after x posts
New usergroup setting - hide optional/custom profile fieldsNew usergroup setting - hide contact details- Links in signature as a nofollow
- ACP 'Find Users' Changes
- Change fields to add 'contains x or is not blank'
- New field - registered in the last x days
- Registration Controls
- Tim's No Spam Pls plugin added into core
- Goodbye Spammer
Matt's Goodbye Spammer tools to be added into core
Associated revisions
WIP Spam Ninja Updates (wip #1726)
WIP Spam Ninja Updates (wip #1726)
WIP Spam Ninja Updates (wip #1726)
WIP Spam Ninja Updates (wip #1726)
WIP Spam Ninja Updates (wip #1726)
WIP Spam Ninja Updates (wip #1726)
WIP Spam Ninja Updates (wip #1726)
Completes Spam Ninja Updates (completes #1726)
Completes Spam Ninja Updates (completes #1726)
Fixes Spam Ninja Updates (fixes #1726)
History
#2 Updated by Tom Moore 8 months ago
r5601 introduces the ability to switch between the default CAPTCHA and reCAPTCHA. It is only preliminary - do not use it - it only works on the registration page. To do: Wiki page, check when settings are saved to ensure public/private key is entered, if public/private key is invalid automatically switch to default CAPTCHA.
#3 Updated by Tom Moore 8 months ago
A few caveats with reCAPTCHA. If turned on, a guest must enter a new CAPTCHA even if they 'preview' a post/thread. There might be a way around this but it's probably long winded and not really essential. At least it protects registrations.
#4 Updated by Tom Moore 8 months ago
- Description updated (diff)
r5616 adds signature controls and a hidden CAPTCHA ability, settable by the user for pure randomness fields.
It also adds the ability to set a minimum post count to custom profile fields. Although, these should also be hidden on the profile too I guess.
#5 Updated by Tom Moore 8 months ago
- Description updated (diff)
- Status changed from Assigned to Resolved
I've opted for Matt's work to go into the Spam Ninja plugin. I guess that's what it's there for (to deliver spam tools) alongside some things from Tim's No Spam Pls plugin.
The rest of the items on the list should be ready to go. SQA should be checking all the features work as expected and please report anything you think might be strange.
#6 Updated by Nathan Malcolm 8 months ago
For the hidden captcha, wouldn't it be better for it to be set as a random string on installation? That way if it's by default 'email3' bots could recognise that. I know Xrumer for one has the ability to learn from fields, and if many forums have it as default, it's close to pointless.
#7 Updated by Stefan T. 7 months ago
- Status changed from Resolved to Feedback
"Leave this field empty:" should be translatable.
@Malcolm: But the bots wouldn't "use" a field with a random name...
#8 Updated by Tom Moore 7 months ago
- Status changed from Feedback to Resolved
- % Done changed from 0 to 100
Applied in changeset r5636.
#10 Updated by Nathan Malcolm 7 months ago
@Stefan T.: A few bots I know of fill out every field, and set values for fields they don't recognize as a pre-defined string. Bots that learn, or are setup to ignore a certain field (Example: email3) will be able to register with ease.
#11 Updated by Stefan T. 7 months ago
I've tested this and it works with email3 but not with a random string...