From (simple) multiple accounts detection to isp/connection fingerprinting with score-based moderating/rejecting logic. These are very effective low-hanging fruit at reducing spam.

Supports migration configuration from the following XF1 add-ons;

• TPU Spam Detect
• Alter ego Detector

See the FAQ Known Issues for known limitations. This is not a turn-key solution, and each site may require customization!

For multiple account detection, supports reporting to reports/threads. And will send reports to the same report/thread. To send to thread you must select the "Multi-account to thread" extra.

For connection fingerprinting more additional information is collected and recorded on the account.

Note; Configuration defaults are conservative, aimed at blocking VPNs and proxies. There are a large number of configuration options for this add-on!

Multiple account handling permissions

• Bypass multiple account checking
• Can enable / disable alerting for user
• Can enable / disable alerting for log
• View reportings.

Use Multiple account to thread add-on to send multiple account reports to threads.

Per-user whitelist:

Multiple account logs per-user:

Related Resources
Known issues

• This is not a turn-key solution for blocking spam, but rather a toolkit.
  • On banning a spammer, it is recommended to check the "User Registration Record" for that user and check the signup IP to see if it is associated with an ISP which provides VPN, hosting, or proxy services but not residential services
    If so, you may wish to consider adding that ISP to be grey listed (ie auto-moderate) or blacklisted (auto-reject).
• "Multi-account to thread" does not support merging threads, it will generate a new report thread if it's target is merged or hard deleted.
• There may be GDPR considerations due to the additional information collected and exposed to staff. This information is currently not purged when the account is deleted.
• Geo location information is not an exact science, and VPN providers are adversarial at ensuring ip-geo location may not be accurate