Alter Ego Detector

Alter Ego Detector 1.7.8

No permission to download
Yeah I was using the addon installer by Chris Deeming I believe that is who coded it :D
Did you have an older version installed? And did any error messages hit XF's error log?

Also, what version of PHP are you using? I've only tested it with PHP 5.4+ and it will probably not work with PHP 5.3 or 5.2
 
The add-on works fine but this is what happened today:
I and another user (also an Admin), seem to have the exact same IP. It keeps detecting it. The odd thing is that we live in different towns. So how and why is this possible?
This addon relies on XF being informed of the correct user IP. If your server isn't setup properly (such as behind a load balancer and such) and invalid IP will be assigned to the user. It could be quite some time in the past that this happened.

After checking "Check IP's", Make sure you set the following entry "Check IP's up to XX minutes old." to be about 5-15 minutes and not blank. Otherwise it will check all IPs going back forever which will give false positives.
 
Did you have an older version installed? And did any error messages hit XF's error log?

Also, what version of PHP are you using? I've only tested it with PHP 5.4+ and it will probably not work with PHP 5.3 or 5.2

5.4, I didnt have an older version installed. I didnt see any errors in the log either.
 
I'm pleased to take over development and support of this addon from @Liam W.

5.4, I didnt have an older version installed. I didnt see any errors in the log either.
The white page is your webserver/php config eating the error message. Have you checked your php-fpm or webserver error logs to see if it gave any hints?

I would suggest enabling XenForo's debug mode for your site(remember to disable it!) and then trying to install again to see if it provides an error message. Otherwise, you may need to adjust your php config so it displays errors to users.

Without any sort of error message, this is difficult to debug.
 
I like the cookie lifespan setting. That should help with false positives for people using library computers and such
 
  • Like
Reactions: Xon
Xon updated Alter Ego Detector with a new update entry:

Bugfix release

BugFixes:
  • Updated missed thread & PM title to include both usernames.
  • Issue with whitespace being added to the wrong spots in the .xml file, causing some options to break.
Known bug:
  • Reports for Alter Egos of Alter Egos are not being correctly stored. I will hopefully have a fix within a day or so. This is a fairly old bug, and is the result of silent data truncation.

Read the rest of this update entry...
 
@Xon

Thanks for attending to the cookie lifespan.

I'd like, if I may, to resurrect a request made by Stuart Wright viz:
..... the ability to whitelist specific user pair combinations so they don't fire the detector again

This would be instead of simply suppressing all subsequent reports automatically (which is what I presume you mean by "Only 1 report per alter ego pair made").

I suppose that this would be a case of us marking the pair (effectively) "already reported" manually rather than it happening automatically which is what I presume is presently the case.

I'd prefer to do this manually because I see three possible match types:

1: The pair is honest and genuine. In which case I want it suppressed. (Let me mark it as suppressed).
2: The pair is dishonest. In which case, I'll take some action (eg a ban) and I'm done with it so I'll file the report as complete. However, future reports do not want suppressing in case of - oh, I dunno - the ban being lifted after an appeal, or somesuch. (I won't mark it)
3: Inconclusive. Research is complete but nothing certain one way or the other. I don't want the report remaining in the "inbox", but equally I don't want to lose sight of the pair. In which case I want to carry on getting reports so I can research again. (Again - I won't mark it).

For more rationale as to why this needs to be the exact PAIR and not any individual accounr permission, there is a discussion in posts 260 and onwards in the thread:
https://xenforo.com/community/threads/alter-ego-detector.60972/page-14

Thanks
 
  • Like
Reactions: Xon
@Harpers Tate I've got another update I'm just testing which improves alter-ego of alter-ego reporting. But I'm not sure if it is in a useful direction for you.

@Xon

Thanks for attending to the cookie lifespan.
Not a problem! I've set this to 10 years personally, as I boggle at people keeping their devices for that long. At worse I'll make an update which will cause the cookie to be re-set with a new expiry date.


This would be instead of simply suppressing all subsequent reports automatically (which is what I presume you mean by "Only 1 report per alter ego pair made").
Correct.

I suppose that this would be a case of us marking the pair (effectively) "already reported" manually rather than it happening automatically which is what I presume is presently the case.
The system gives you the option to supress duplicate reports for the same pair by report state.


permit_duplicate_reporting.webp
So for example; you can have Assigned/Resolved not bump the report. But allow Open/Rejected to bump it to the top. Or perhaps allow only Rejected to bump it.

I'd prefer to do this manually because I see three possible match types:

1: The pair is honest and genuine. In which case I want it suppressed. (Let me mark it as suppressed).
2: The pair is dishonest. In which case, I'll take some action (eg a ban) and I'm done with it so I'll file the report as complete. However, future reports do not want suppressing in case of - oh, I dunno - the ban being lifted after an appeal, or somesuch. (I won't mark it)
3: Inconclusive. Research is complete but nothing certain one way or the other. I don't want the report remaining in the "inbox", but equally I don't want to lose sight of the pair. In which case I want to carry on getting reports so I can research again. (Again - I won't mark it).
I see this sort of investigation on my own sites, and definitely want to accommodate it.

For more rationale as to why this needs to be the exact PAIR and not any individual accounr permission, there is a discussion in posts 260 and onwards in the thread:
https://xenforo.com/community/threads/alter-ego-detector.60972/page-14
There is a wrinkle in how I've improved/fixed the alter-ego of alter-ego reporting.

Fundamentally, this addon needs to pick a user to peg the reports to. It picks the lowest user id and tries to assign reports to it. This forward only linking is problematic, and may require the addon to add a comment to the other report if it exists.

Changing this will require a fairly significant redesign, as I need to make the addon itself aware of all aspects of the alter-ego relationships rather than hacking it into the report. This will also reduce how much spam the PM and Thread reporting options create. I'm not sure about when I can scheduling that sort of large rewrite in.

For example; given 4 accounts.
two_reports.webp

5 accounts, but generating a reference between xon2 -> xon4
three_reports.webp

Now what the 'xon2 has 2 alter egos!' report looks like:
report_view.webp


Note; it only adds users to the list of alter egos detected for the first account once.
 
Last edited:
Can we choose the name of the cookie so that we continue with the cookies already out there with the other addon we have running at the moment?
Just picking the cookie name would not be enough, as it is the contents of the cookie which is also important.

Can you start a PM with me so we can discussion what would be required for a potential migration? I'll need a few bits of information, such as a sample of your existing cookie, and a look at the table schema the other addon uses.

Can this be installed alongside another similar addon or will only one work at a time?
This addon doesn't do anything which would break compatibility, so assuming the other addon is hooking XF properly and not preventing XF functionality from being called during login & registration they should work together.

You would however get multiple reports for the same pair of alter-egos.
 
This addon doesn't do anything which would break compatibility, so assuming the other addon is hooking XF properly and not preventing XF functionality from being called during login & registration they should work together.

You would however get multiple reports for the same pair of alter-egos.

I'm just planning to run two of these side by side and see which one picks up more multiple accounts then stick with the one which works better. I like yours. It seems light.
 
Can this be installed alongside another similar addon or will only one work at a time?

Our add-on [WMTech] Sticky Multiple Account Info can be installed beside this add-on without problems (you can even disable any reporting to prevent "double" reports). Our test (with previous versions of this add-on) showed that our add-on will catch more real multiple accounts, because it does not rely at IP or cookie detection. However most multiple accounts will be catched by both of them.

Also our add-on does not work with "pairs" of accounts, but rather "sets" of accounts accessed with the same hardware. The main diference between both add-ons is that our add-on focuses at "Information" rather than "Detection". Reliable detection is a premise for good information. Also our add-on is not free unfortunatelly.

I'm just planning to run two of these side by side and see which one picks up more multiple accounts then stick with the one which works better. I like yours. It seems light.

Please keep in mind that you may get "more" reports with this add-on because false positives are possible. Especially with IP detection. So "more" reports may not always be a quality indicator. ;) Our add-on takes special care to not report any false positives. It would rather not report than report a false positive. We needed reliable detection to provide reliable information. Our add-on is also as lightweight as this add-on and used at many big boards without any performance impact (which we take special care of with all our add-ons). In addition with our add-on you can also set how light-weight you like it to be (for the price of having to wait longer for a detection in some cases).

Hope this helps for your information.

I do like this add-on has a new developer now. So people will have a better choice. And choice is good!
 
I'm just planning to run two of these side by side and see which one picks up more multiple accounts then stick with the one which works better. I like yours. It seems light.
Both addons fundamentally work on client-side metadata which most browsers are moving to support purging or controlled by privacy settings. These can be 'evercookies' of various types, or even css history knocking (and similar) if you want to be fancy.

It is quite easy to avoid either addon's detection by just picking up a modern smartphone on 2g/3g/4g and using the browser in private mode for one account and using a desktop for another.

Ultimately all this addon is designed to accomplish is to catch low hanging fruit, and to publish detection via existing front-end interfaces.

Please keep in mind that you may get "more" reports with this add-on because false positives are possible.
False positives are always possible. Space Battles moderators have literally asked for photographic evidence to help distinguish between close friends, siblings and couples using the same computer, same profile, and same browser.

IP Check is off by default, and I implemented a default timeout on the window for the ip check so people should get less false-positives when using it.

Our add-on is also as lightweight as this add-on and used at many big boards without any performance impact (which we take special care of with all our add-ons).
All my addons are written for Big Boards in mind, as they are written for use cases discovered by Space Battles and Sufficient Velocity which both have very active userbases.

That said, the Can Warn Staff addon is fairly heavy weight in comparison to all of my other addons.
 
Last edited:
Back
Top Bottom