Moshe1010
Well-known member
You can PM me with a priceThe alter-ego detector really isn't that flexible in how it does the matching, and I will have to ask if you are willing to funding to change that detector matching logic.
You can PM me with a priceThe alter-ego detector really isn't that flexible in how it does the matching, and I will have to ask if you are willing to funding to change that detector matching logic.
Sorry for a lack of follow up, but can you PM me the stack trace so I can see where it is failing?
We've had a few "false positives" pop up with IPs set to be checked, but having that option turned on helps us more when a troublemaker deletes their cookie and tries to return. Being able to whitelist certain IP addresses that we know are OK, some proxies for example, would come in handy to eliminate future false positives.Is there a way to whitelist a specific IP address?
You can. Just create a usergroup called 'Alter-ego Bypass' ... and set the alter-ego bypass permission on it - then apply it to the accounts you want to exclude from checking.Is there any chance this can get updated to prevent reporting the same members over and over again? We have a group of users that are allowed to have two usernames, but everyday we get loads of "alter ego" reports from these same users that log in every day. It would be nice if we could perhaps exclude a secondary usergroup? Or stop it from reporting the same users every day? Thanks.
Well that was easy, lol, thanks for the tip.You can. Just create a usergroup called 'Alter-ego Bypass' ... and set the alter-ego bypass permission on it - then apply it to the accounts you want to exclude from checking.
"Resolving" a report will block it from reporting that particular set of users. Alternatively use the 'alter-ego bypass' permission.Is there any chance this can get updated to prevent reporting the same members over and over again? We have a group of users that are allowed to have two usernames, but everyday we get loads of "alter ego" reports from these same users that log in every day. It would be nice if we could perhaps exclude a secondary usergroup? Or stop it from reporting the same users every day? Thanks.
I assume that is done in the Report Center? I don't use the report center on my forum, I use the 'send reports into forum' option."Resolving" a report will block it from reporting that particular set of users.
Next version will have it. I've been fairly busy so I'm hoping to release it start of next week or the week after.how can I add exception for some members of the forums based on there IP address?
Bugfix
Feature
- Ensure the report is bumped on multiple socks against the same user when the report is in a state which is suppressed for sending duplicates reports.
- Option to require moderated users todo email confirmation rather than being accepted or rejected.
- Ability to change detection logic from requiring cookie or IP to cookie and ip, or just matching on cookie.
- If IP matching is enabled, the IP is now reported.
- Ability to whitelist...
I got excited but then saw it was for IP's only. Any chance we could whitelist usernames? Thank you.Ability to whitelist...
I'm not really sure why you'ld want to whitelist by username.I got excited but then saw it was for IP's only. Any chance we could whitelist usernames? Thank you.
This is awkward, because we have some members who have upgraded their memberships with a subscription, and I don't want to mess this setup up.You can. Just create a usergroup called 'Alter-ego Bypass' ... and set the alter-ego bypass permission on it - then apply it to the accounts you want to exclude from checking.
This is awkward, because we have some members who have upgraded their memberships with a subscription, and I don't want to mess this setup up.
This is the issue I have as well with quite a few of my members, thus the request for being able to whitelist usernames, in my country we have shared IP's so whitelisting an IP address will not work in my case.Among our members, we have one married couple who uses computers on the same ISP. They are flagged regularly.
The current user permissions have been carefully designed to work with our setup over a period of several years. I don't want to go through a silly process just to flag a false positive. Why not a simple "Ignore" checkbox? Why make it harder than it needs to be?How would it mess up the upgrades?
It won't impact on any subscriptions or other usergroups - since all you are doing it setting a single permission to allow bypassing of the alter-ego detection. It takes a matter of seconds to create this usergroup, and a few seconds to add it it any user account - and that's it, they won't be reported again.This is awkward, because we have some members who have upgraded their memberships with a subscription, and I don't want to mess this setup up.
It really isn't hard - just login to the ACP, go to the user account, tick the bypass usergroup, save, exit.Why make it harder than it needs to be?
We use essential cookies to make this site work, and optional cookies to enhance your experience.