People ask me about making money from AdSense all the time. While I usually will offer little tips and tricks that I’ve learned along the way, one thing I want to make sure that new AdSense publishers know is what NOT to do.
The number one thing that you should NOT do is STEAL OTHER PEOPLE’S CONTENT. Yes, I know the guy who sold you the video or the eBook said it was okay. Guess what, he has your $97 bucks, and you’re about five minutes away from being up shit creek without a paddle, as you lose your web hosting, your domain names, and most importantly, your AdSense account, all because you ripped someone off.
If I catch you stealing my content, your ass is grass. (This obviously doesn’t apply if I gave you permission to use it.)
This content was stolen from Michael Hampton.
Copyright © 2006 Michael Hampton. All rights reserved. This material may not be published, broadcast, rewritten or redistributed.
September 19, 2006
Posted by
Michael Hampton |
AdSense, Advertising, Bad Behavior, Blog Spam, Google, Link Farm, Personal, Spam, Splog |
|
2 Comments
People ask me about making money from AdSense all the time. While I usually will offer little tips and tricks that I’ve learned along the way, one thing I want to make sure that new AdSense publishers know is what NOT to do.
The number one thing that you should NOT do is STEAL OTHER PEOPLE’S CONTENT. Yes, I know the guy who sold you the video or the eBook said it was okay. Guess what, he has your $97 bucks, and you’re about five minutes away from being up shit creek without a paddle, as you lose your web hosting, your domain names, and most importantly, your AdSense account, all because you ripped someone off.
If I catch you stealing my content, your ass is grass. (This obviously doesn’t apply if I gave you permission to use it.)
This content was stolen from Michael Hampton.
Copyright © 2006 Michael Hampton. All rights reserved. This material may not be published, broadcast, rewritten or redistributed.
September 19, 2006
Posted by
Michael Hampton |
AdSense, Advertising, Bad Behavior, Blog Spam, Google, Link Farm, Personal, Spam, Splog |
|
2 Comments
I received a report by email this morning from a user who successfully installed Bad Behavior on her GoDaddy-hosted blogs.
This is significant because for a very long time GoDaddy web hosting users could not run Bad Behavior, due to an apparently misconfigured reverse proxy which GoDaddy was running. The problem went unresolved for well over a year.
But last month I received an email from someone in GoDaddy’s security department who said he would look into the matter. It seems someone did something, as it appears people are able to use Bad Behavior on GoDaddy shared hosting now.
In my own testing against GoDaddy shared hosting sites, it appears that the header mangling which the reverse proxy was doing is no longer taking place, so Bad Behavior should run fine on GoDaddy shared hosting sites now.
If you use GoDaddy shared hosting, but have not been using Bad Behavior because it blocked everything when installed, please try it again and report back. Thank you!
September 19, 2006
Posted by
Michael Hampton |
Bad Behavior, GoDaddy |
|
No Comments
I’ve rebuilt the Bad Behavior 2.0.6 package due to an error which causes users to be blocked in rare circumstances.
If you receive a user complaint that they were blocked, and when they click the “fix this yourself” link and are told they have a “Dynamic IP address,” or that they are not listed on any blacklists, then you are affected by this problem.
This problem occurs when the Web server has a search domain listed in the /etc/resolv.conf file, and the listed domain uses wildcard DNS. This is a very uncommon configuration, as the vast majority of sites either do not list any search domains, or list a domain which doesn’t use wildcard DNS.
Bad Behavior has been altered to bypass the search domain if it is listed, thereby solving the problem. Simply re-download Bad Behavior 2.0.6 to obtain the fix.
September 19, 2006
Posted by
Michael Hampton |
Bad Behavior |
|
7 Comments