It just seems a bit of a potch to me when there are better and, IMHO, more flexible ways of doing it.iWisdom wrote:The blacklists are pre-populated with a list of known offenders.
It just seems a bit of a potch to me when there are better and, IMHO, more flexible ways of doing it.iWisdom wrote:The blacklists are pre-populated with a list of known offenders.
Until you find yourself on a number of blacklists through no fault of your own.Martin Truckenbrodt wrote:And please don't forget: Blocking is much more user friendly as CAPTCHA it is.
Whether blacklisting is bad is open for debate, and it's true that an IP doesn't represent a user or even a specific machine in some cases.ToonArmy wrote:I've looked at the MOD more than once, but the simple matter is blacklisting is bad. You place the decisions over who can access your board to an external provider, even if you use multiple providers and collate the results you could end up with a false positive. An IP address does not represent an individual user, blocking an IP might unintentionally block legitimate users.
This topic is intended to discuss non-invasive anti-bot measures. Chiefly plugins and configuration settings, but not MODs. Packaging a blacklist based CAPTCHA into a plugin is perfectly feasible, but won't be provided as a default plugin.Pony99CA wrote:
Alternatively, could blacklisting be built into a CAPTCHA plug-in so that no user interaction is required (the "user" input would essentially be the IP address and E-mail address which phpBB already knows)? If so, maybe that would answer Martin's objections (although CAPTCHAs aren't able to be presented for every user that posts, just guest users).
Steve
Code: Select all
case FIELD_TEXT:
if (empty($field_value) && !$field_data['field_required'])
{
return false;
}
else if (empty($field_value) && $field_data['field_required'])
Code: Select all
case FIELD_TEXT:
if (empty($field_value) && !$field_data['field_required'])
{
return false;
}
else if ($field_data['field_required'] && strtolower($field_value) !== 'kiwi')
I took that option at face value and, since I didn't want my users to decipher a garbled random code, set it as disabled.Enable visual confirmation for registrations:
Requires new users to enter a random code matching an image to help prevent mass registrations.
Thanks for your help.Enable antispam confirmation for registrations:
Requires new users to pass a human-only test to help prevent mass registrations.