Signup abuse detection and blocking [Paid] 1.13.6

[Xon]

Xon updated Signup abuse detection and blocking with a new update entry:

1.13.6 - Maintainance update

• Require Standard Library by Xon v1.17.0+
  • Uses standardized route building to avoid conflicts with other 3rd party add-ons
  • Add specific message in the thread view for why a user can't reply to a thread when the per-day limit has been reached

Read the rest of this update entry...

 

[Dragonfruit]

Hi @Xon
Just wondering if there's plans to implement a log for failed/declined registrations?

Thanks!

 

[Forsaken]

Hi @Xon
Just wondering if there's plans to implement a log for failed/declined registrations?

Thanks!

There is one: /admin.php?logs/spam-trigger/

 

[Dragonfruit]

There is one: /admin.php?logs/spam-trigger/

This seems to only log the ones that get through, not fail because they're failing the test as bots.

 

[Xon]

This seems to only log the ones that get through, not fail because they're failing the test as bots.

Spam-trigger log includes failed attempts, it is just hard to search/filter without my Admin Log Search add-on.

 

[Dragonfruit]

Spam-trigger log includes failed attempts, it is just hard to search/filter without my Admin Log Search add-on.

Oh, there's only a small handful of logs in there. I suspect then there's not many getting past the StopForumSpam.

I might disable SFS and give that a test. Thanks!

 

[Case]

I've just signed up for an ipregistry.co account. Presumably, the API key is what goes in the Connection profiling - ASN > Use ipregistry.co settings box? It's not clear from the form field label.

 

[Xon]

I've just signed up for an ipregistry.co account. Presumably, the API key is what goes in the Connection profiling - ASN > Use ipregistry.co settings box? It's not clear from the form field label.

Yes, that is what the field is for.