SFS Global Antispam Statistics

[mberasategi]

Hi,

Thanks for the module, spam in Pligg is a real nightmare. However, I'm not sure if «add [spammers] to the global list through the user management (click on "Add user to global spammer database". This adds the users information to the blacklist and will not let them register on any other Pligg site that is using this module)» is working... A popup window opens but does not say anything, I have to manually close it.

[PurpleCow]

Thank you soo much for giving this module away for free. It greatly helps.
I used this widget and module in v1.1.3 and it seems to be working. Has anyone else tested this on Pligg 1v.1.3 - and is it working for you?

One observation though: I signed up with my email id and the admin widget said, it has blocked my mail ID and my user account registration. However I was able to confirm my registration following the link in my mail and also login.

What would this mean - working / NOT working?
Is it an issue?
If it is an issue - issue with the widget/module or SFS not really blocking the user?

Also - i tried to navigate to individual user account page and tried to submit the user email to SFS database and a blank window popped up without any confirmation. (see the attached) - not sure what it means...
UPDATE on my Observation above: I checked my account at SFS after submission of spammy users and they shown up fine at their end. Do the question of bank screen attached remains - is it supposed to display confirmation of submission to SFS?

- Another quick question: Is there any way to mass submit spam users to SFS? like an option (column) in manage >> users section of admin?
- Also - when I submit a spammy user to SFS - are they kill-spammed in my pligg site or does their account still continue to exist?
- I have removed register.php which comes with v1.1.3 and have replaced it with register.php file packaged in this module. But I see the one with v.1.1.3 is not the same as one in this module (apart from //###STOP FORUM SPAM PATCH### related changes). Should I just copy paste all the code that be below //###STOP FORUM SPAM PATCH### section to the register.php which comes with v1.1.3?

Thanks much in advance...

[web20guy]

Getting an API key from stopforumspam must be impossible.

I tried two different emails that are not know to be spam related address.

There system blacklisted them both and denied me access....

I call <bs>

[ChuckRoast]

Getting an API key from stopforumspam must be impossible.

I tried two different emails that are not know to be spam related address.

There system blacklisted them both and denied me access....

I call <bs>

I've never had a problem getting an API key from them.
Don't use free email providers. Use an email address from your own domain.

[web20guy]

Use an email address from your own domain.

Yep...

That's the ticket. Thanks.

[ChuckRoast]

This module has now been updated to work with Pligg version 1.1.5 through 1.1.2 You can download it from the first page in this forum thread.

[ChuckRoast]

Module and Widget updated for Pligg 1.2.2

[web20guy]

I read all the problems that others have with spam and bots with their pligg sites.

Then I read all the hoopla of 115000 users and climbing and 2k hits a day. Time to monetize!!

My thoughts are it's "mighty tough to monetize fake traffic".

I feel for all of you.......... yo-yo rides are tough to stay on.

I installed SFS the Antispam module along with this widget back in March, 2011. Glad to see this has been updated! Along with REDC, Spam trigger and the Karma module fake users are all but a thing of the past.

To-date: Almost a 1/2 million registrations blocked. Love it!

antispam.png

[borix]

There is a seemingly logic error with the register_check_spammer function in the register.php file provided with the module. Here's the function for reference, I have highlighted in red the lines (near the end), where the logic error persists:

//### STOP FORUM SPAM PATCH###
function register_check_spammer($username,$userip,$email){
	$isSpammer = false;
	$content = file_get_contents("http://www.stopforumspam.com/api?ip=".$userip);
	if ($content !== false) {
	  $isSpammer = strpos($content,"yes")?true:$isSpammer;
		} else {
		 //do nothing?
		}
		$content = file_get_contents("http://www.stopforumspam.com/api?ip=".$_SERVER['REMOTE_ADDR']);
		if ($content !== false) {
		  $isSpammer = strpos($content,"yes")?true:$isSpammer;
		} else {
		 //do nothing?
		}
		$content = file_get_contents("http://www.stopforumspam.com/api?email=".$email);
		if ($content !== false) {
		  $isSpammer = strpos($content,"yes")?true:$isSpammer;
		} else {
		 //do nothing?
		}
		$logstr = "Last Blocked ".$username.", ".$userip.", ".$email.", ".date("F j - Y - g:i a")."\r\n";
		file_put_contents('registerLog.txt',$logstr, FILE_APPEND);
		return $isSpammer;
}
//###STOP FORUM SPAM PATCH###

This function is called every time a new user registered. Now, the two lines in red will be executed whether or not the user is an alleged spammer and will thus be logged in the registerLog.txt file. This is very confusing. I propose either moving these two lines to the other SFS-related piece of code in register.php or to enclose them in an if($isSpammer) condition. The other piece of code they can go into is at the end of function register_check_errors:

//###STOP FORUM SPAM PATCH###
	if(register_check_spammer(trim($username),trim($userip),trim($email))){
			$form_username_error[] = $main_smarty->get_config_vars('PLIGG_Visual_Register_Error_UserInvalid');
			//we DO NOT tell them that their IP address is banned!
			$error = true;
// log the spammer:
$logstr = "Last Blocked ".$username.", ".$userip.", ".$email.", ".date("F j - Y - g:i a")."\r\n";
		file_put_contents('registerLog.txt',$logstr, FILE_APPEND);
	}
//###STOP FORUM SPAM PATCH###

This is not really a critical error; however, it may induce the admin to conclude that the registered user is a spammer, while they're genuine posters... It has happened to me twice today, it's good I caught it now. I noticed it happened to another user a month ago, and now they're gone forever...