Who might this New User be?

Hiyas,

When a new user registers your board, this hack analyzes his email, password, ip address and isp (ranged ip) against existing board members and produces a sorted list with probabilities about who this new user might be. (See screenshot below). This list will be emailed to you with new user notification mail. (The probabilities can be modified by you so it's you who decide how matched results are sorted and ranked, dont blame me!)

Tested and will work better in relatively smaller boards (less than 3000 members). If you have a small board, this hack may help you a bit to track and pinpoint existing users if they re-register with different usernames. For large boards, IMO it's pointless to track new users anyway..

As far as I know it will work with ANY vbulletin version so feel free to try. Installation is very easy, actually 2 simple steps and will take you 2 minutes to apply..

If they change their both ip, isp, password and email, the hack cant get them, yeah I know! This is the best we can do with computer technologies. If you have higher expectations and demands, you may regard consulting a "Seer"..

If you liked this hack, I suggest checking Jawelin's nice Paranoid dupe user buster when moderating Hack too. They make a good couple and I use them both.

Click Install button, if you installed the hack, thank you!

Enjoy! \=^))

Logician

[Logician]

Yesterday at 01:59 AM XFLBret said this in Post #40
hello.

first off. i want to say that this is one of my favorite hacks. as far as administrative hacks, this is by far my favorite.

it worked like a champ on my old host, no complaints at all. but i have moed hosts, and then upgraded my board to 2.3.0, and now I can't get this hack to work the way I want it to.

first off, the email no longer sends me the password for each user. how do i correct that error?

second, the email has a blank line between each line, as if it were separated by a <br> thing or something. I double-checked the template, and it looks fine.

help!

I don't have access to 2.3.0 code as I didn't renew my expired membership so hard to debug for me blindly. But I know that 2.3.0 put all mailing actions into a function and PHP functions does not access to global variables. So you have to find the mailing function and globalize password variable to get it by mail via this line:

PHP Code:

global $password; 


As I don't have the code, I can not help you with its location, sorry..

As for extra line, again hard to debug as I don't use that version, but you can try to remove \n at the end of

PHP Code:

$match_user_final.=(string)($i+1)."- ".${$result}[probability]."% => ".${$result}[username]." (id:".${$result}[userid].") ".${$result}[email]."  ".${$result}[matches]."\n"; 


and see if it helps.

[Morgalis]

I'm using this on a really large community, but I am pretty aware of the people that I am looking for.

I would like to be able to extend the search time for the script as I get this error

Fatal error: Maximum execution time of 30 seconds exceeded in /usr/home/diabloworld/forums/admin/user.php on line 1341

How can I do this?

GREAT hack btw, you just need to have more patience and awareness with a large forum I think.

[Logician]

Today at 02:38 PM Morgalis said this in Post #42
I'm using this on a really large community, but I am pretty aware of the people that I am looking for.

I would like to be able to extend the search time for the script as I get this error

Fatal error: Maximum execution time of 30 seconds exceeded in /usr/home/diabloworld/forums/admin/user.php on line 1341

You can insert

PHP Code:

set_time_limit(600); 


right before hack code to avoid this error.

GREAT hack btw, you just need to have more patience and awareness with a large forum I think.

You are missing the fact that technological structure of the hack does not let it be used in large forum, it is not related to my awareness.

This is because:
The hack checks all IPs in the post database and user database to make an extensive and successful matching and to complete this search quickly and without making your server busy, your database size must be small (ie your board must be a small board). If you use the hack in a large board like yours, it is inevitable that you'll run into problems just like the error you have in your hands now. It shows that the hack can not finish matching the users in 30 seconds everytime it runs so its putting a burden to your server to compare a huge list. My solution can avoid this error but it does not show that it is ok to use the hack with your board. Because my solution above just makes sure you don't get the error but the burden in your server will there everytime someone registers and more imporatly he will have a looong waiting time when he clicks "register" button even if you don't have an error message.

This is inevitable.

The only chance is to avoid it is to recode the hack so that it will not make comparisons in the entire database (this means it will produce less successful results at the end).

So as you can see we have a technical restriction here, regarding large boards..

[gmarik]

Is this working on 2.3 as well?

[Mr. Brian]

Is it possible to track back old users?

thanks

[Logician]

Today at 09:28 PM Matthew Lam said this in Post #45
Is it possible to track back old users?

question is not clear to me but the hack will check the entire database so you old user is still a user (ie not deleted from DB), he will be matched..

[94supratt]

05-24-03 at 10:58 AM gmarik said this in Post #44
Is this working on 2.3 as well?

Any news?

[Bison]

It Sure is ...

[mariannet]

I was finding this hack very helpful, but after integrating Hivemail with vBulletin I had to remove the code from "register.php". Can you please tell med how to change the "Who might this New User be?" code bit in "register.php" to make it work again?

I have included the code from Hivemail that I have added:

// @@@@@@@@@@
// <hivemail>
$hivemail_filepath = '/home/yoursite/public_html/hivemail';

if ($action == 'mailsignup') {
  if ($bbuserinfo['userid'] != 0) {
    $action = 'register';
    define('VB_PLUGIN', true);
    require($hivemail_filepath.'/includes/vbulletin_plugin.php');
    if ($bbuserinfo['hiveuserid'] != 0 and
      $hiveuser = $DB_Hive->query_first("
        SELECT userid FROM hive_user
        WHERE userid = $bbuserinfo[hiveuserid]
      ")) {
      header('Location: usercp.php');
    }
    eval('dooutput("'.gettemplate('hivemail_signup').'");');
    exit;
  } else {
    $action = 'signup';
  }
}

if ($HTTP_POST_VARS['action'] == 'addmail') {
  if ($bbuserinfo['userid'] != 0) {
    $action = 'register';
    define('VB_PLUGIN', true);
    require($hivemail_filepath.'/includes/vbulletin_plugin.php');
    if ($bbuserinfo['hiveuserid'] != 0 and
      $hiveuser = $DB_Hive->query_first("
        SELECT userid FROM hive_user
        WHERE userid = $bbuserinfo[hiveuserid]
      ")) {
      header('Location: usercp.php');
    }
    $email = $bbuserinfo['email'];
    hivemail_register_user($bbuserinfo['userid'], false);
    hivemail_update_password($bbuserinfo['password'], $bbuserinfo['userid']);
    eval('standardredirect("'.gettemplate('hivemail_thankyou').'", "usercp.php");');    
    exit;
  } else {
    $action = 'signup';
  }
}

define('VB_PLUGIN', true);
require($hivemail_filepath.'/includes/vbulletin_plugin.php');
if (($action == 'signup' or $action == 'register') and
  $bbuserinfo['userid'] != 0 and
  !$allowmultiregs and
  ($bbuserinfo['hiveuserid'] == 0 or
  !$hiveuser = $DB_Hive->query_first("
    SELECT userid FROM hive_user
    WHERE userid = $bbuserinfo[hiveuserid]
  "))) {
  header('Location: register.php?action=mailsignup');
  exit;
}
// </hivemail>
// @@@@@@@@@@@

  // @@@@@@@@@@
  // <hivemail>
  if ($hive_signup == 'yes') {
    hivemail_register_user($userid);
  }
  // </hivemail>
  // @@@@@@@@@@@

[Logician]

I don't know why you had to remove my code while installing hivemail code? You didn't mention where you inserted it, nor I'm familiar with hivemail but I believe my code should not clash with hivemail's code unless it bypasses vb's default registration project to register the user to vb itself. This would be unlikely so my hack should still work. But if this is the case, then my hack will never work because if hivemail is overtaking the registration process, then it means that hivemail should be hacked to achieve what this hack is doing.