Alter Ego Detector 1.7.8

[Niro]

@Xon we use this important add-on in our current XF1 forum but are looking to migrate to XF2 and feel we can't do it without this add-on. Appreciate you're probably mega busy at the moment, but any timeline on when you think you can get an XF2 version of this up?

Hello,

A XF2 version is available, it is still on beta, more infos here :

https://atelieraphelion.com/products/signup-abuse-detection-and-blocking.64/

 

[Bimble]

Thanks @Niro - much appreciated.

 

[Xon]

Signup abuse detection and blocking is being used successfully on a few sites now, I plan to bring it out of beta (and release here) fairly soon.

 

[Bimble]

Thanks for the update @Xon

 

[Movie Prop Sites]

Signup abuse detection and blocking is being used successfully on a few sites now, I plan to bring it out of beta (and release here) fairly soon.

Like Bimble, we won't move our sites to XF2 without this.

 

[sbj]

There is also a free version, but Xon's will be more advanced I assume.

 

[Xon]

There is also a free version, but Xon's will be more advanced I assume.

My add-on records what threads/conversations it's reports to and doesn't create duplicate threads, and provides an easy way to see all alter-ego detection events for a given user. The fingerprint detection in that free version doesn't don't handle IP changes and a few other downsides.

 

[webbouk]

Basically Xon what you are trying to say is it doesn't work as one would expect
I can testify to that, and the support was lacking to say the least

 

[dethfire]

My add-on records what threads/conversations it's reports to and doesn't create duplicate threads, and provides an easy way to see all alter-ego detection events for a given user. The fingerprint detection in that free version doesn't don't handle IP changes and a few other downsides.

Is this out yet?

 

[TickTackk]

Is this out yet?

Signup abuse detection and blocking

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...

xenforo.com

 

[Gossipy]

Hey @Xon - an error here,

XenForo_Exception: Please enter at least one valid recipient. - library/XenForo/DataWriter.php:1359
Generated By: Skato, 1 minute ago

#0 /var/www/wweforums.net/httpdocs/library/XenForo/DataWriter.php(1401): XenForo_DataWriter->_haveErrorsPreventSave()
#1 /var/www/wweforums.net/httpdocs/library/LiamW/AlterEgoDetector/XenForo/Model/SpamPrevention.php(737): XenForo_DataWriter->save()
#2 /var/www/wweforums.net/httpdocs/library/LiamW/AlterEgoDetector/XenForo/ControllerPublic/Login.php(45): LiamW_AlterEgoDetector_XenForo_Model_SpamPrevention->processAlterEgoDetection(Array, Array, Object(XenForo_Phrase))
#3 /var/www/wweforums.net/httpdocs/library/XenForo/FrontController.php(351): LiamW_AlterEgoDetector_XenForo_ControllerPublic_Login->actionLogin()
#4 /var/www/wweforums.net/httpdocs/library/XenForo/FrontController.php(134): XenForo_FrontController->dispatch(Object(XenForo_RouteMatch))
#5 /var/www//wweforums.net/httpdocs/index.php(13): XenForo_FrontController->run()
#6 {main}

any idea?

We are also getting this error with the latest version of plug-in.

Please ensure the username matches exactly, the lookup system is kinda dumb.

It matches exactly, but it contains a space (i.e. it's two words). Could that be causing the error?

 

[Xon]

We are also getting this error with the latest version of plug-in.



It matches exactly, but it contains a space (i.e. it's two words). Could that be causing the error?

This code path hasn't changed for a very long time, please confirm someone hasn't renamed the account on you.

 

[Gossipy]

This code path hasn't changed for a very long time, please confirm someone hasn't renamed the account on you.

Thank you for such a fast response!!

I'm 10000% correct the username is correct in the option setting. I even thought about some kind of hidden character messing things up so I literally copied and pasted the username from the AdminCP user page into the option form and am still getting the error.

 

[Xon]

I'm 10000% correct the username is correct in the option setting. I even thought about some kind of hidden character messing things up so I literally copied and pasted the username from the AdminCP user page into the option form and am still getting the error.

Please check the User ID/Username settings that the notifications are being created from. They need to be a valid user, and it may be throwing a weird error if it isn't correct. Conversations could be hitting some internal logic checks preventing sending to the recipient user from the user you have configured to send from.

I'ld recommend using the report or thread reporting option as a work-around.

 

[Gossipy]

Please check the User ID/Username settings that the notifications are being created from. They need to be a valid user, and it may be throwing a weird error if it isn't correct. Conversations could be hitting some internal logic checks preventing sending to the recipient user from the user you have configured to send from.

I'ld recommend using the report or thread reporting option as a work-around.

Thank you again, we will follow your advice.

Update: We were foolishly setting the sender and receiver to the same user. Fixed.

 

[Gossipy]

Can someone help me clarify something?

If this plugin generates a notification, for example:

On login, it looks like [User A] is an alter ego of [User Z]...

[User A], Triggered detection methods:
- Cookie

In the above example, is the report generated when a device previously logged in as User A logs in as User Z? Or vice versa?

Thank you.

 

[Xon]

In the above example, is the report generated when a device previously logged in as User A logs in as User Z?

This should be the case

 

[Gossipy]

This should be the case

Thanks, so it sounds like (in the above example) it is triggered by User Z logging in using a device that was previously used by User A. So it is, upon User Z's login, detecting the cookie left behind by the previous User A login.

Thanks again for such fast responses. Very helpful.

 

[dethfire]

Had a few hundred of these show up after upgrade from 1.5.22 to 2.1RC2. Report content-type was alterego.

ErrorException: Error doing JSON conversion xf_report.content_info (report_id=24745): Malformed UTF-8 characters, possibly incorrectly encoded src/XF/Error.php:75

Stack trace

#0 src/XF.php(187): XF\Error->logError('Error doing JSO...', true)
#1 src/XF/Install/InstallHelperTrait.php(173): XF::logError('Error doing JSO...', true)
#2 src/XF/Install/InstallHelperTrait.php(117): XF\Install\Upgrade\AbstractUpgrade->updateResultsToJson(Array, 'xf_report', Array, Array)
#3 src/XF/Install/InstallHelperTrait.php(42): XF\Install\Upgrade\AbstractUpgrade->tableColumnsToJson('xf_report', Array, Array, 23008, Array, false)
#4 src/XF/Install/Upgrade/2010010-210a.php(464): XF\Install\Upgrade\AbstractUpgrade->entityColumnsToJson('XF:Report', Array, 23008, Array)
#5 src/XF/Cli/Command/Upgrade.php(134): XF\Install\Upgrade\Version2010010->step21(23008, Array, Object(XF\Install\Controller\Upgrade))
#6 src/vendor/symfony/console/Command/Command.php(255): XF\Cli\Command\Upgrade->execute(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#7 src/vendor/symfony/console/Application.php(953): Symfony\Component\Console\Command\Command->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#8 src/vendor/symfony/console/Application.php(248): Symfony\Component\Console\Application->doRunCommand(Object(XF\Cli\Command\Upgrade), Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#9 src/vendor/symfony/console/Application.php(148): Symfony\Component\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#10 src/XF/Cli/Runner.php(63): Symfony\Component\Console\Application->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#11 cmd.php(15): XF\Cli\Runner->run()
#12 {main}

Request state

array(1) {
["cli"] => string(18) "cmd.php xf:upgrade"
}

 

[Xon]

Ugh. Upgrading from XF1 => XF2 (Signup abuse detection and blocking) then upgrading to XF2.1 works.

@dethfire Not sure why this is throwing errors. Probably need to report this to XF1 that reports can potentially have non-utf8 encodable strings in them since it is serialize not json_encode

@Mike @Chris D Any suggestions on this? I'm thinking I might need to run a job in XF1 land to strip out but the minimum data required.