IP Juiced

Wanna know what I’m juiced about today?

We’re undertaking changing the behind-the-scenes to our system to help us understand our members by IP address and the relationship by IP address that each author has to each other. :)

Example: This past Sunday, someone we’ll call David from Canada created 15 accounts with us, all under bogus names and information, but the one thing that was constant was his IP address.

What’s even more fun will be when we can chart the IP addresses matched authors to begin to understand who is related to each other and who is gaming the system vs. legitimate multiple authors sent in from services like SubmitYourArticle.com.

Eventually, I can see a time where we will be able to rank our trust in an author based on their IP address. Just another tool to help us understand or authenticate who each author is or might really be.

Posted by on July 14, 2005 at 11:05 am | 1,772 views

3 Comments »


1
Matthew C. Keegan writes:

I hope this works out for you.

I wonder if you will be able to nail down AOL users who have IP addresses that constantly switch. Still, it is a good idea and encourages those of us who are legitimate to know that we won’t be lumped in with the rest.

Comment provided July 25, 2005 at 10:19 AM

[Reply]

2
Catherine writes:

What about asking authors to give their IP address when they register and that part of the system?

Comment provided August 11, 2005 at 4:35 PM

[Reply]

3
Christopher Knight writes:

Catherine,

We are now automatically appending each authors IP address and reverseDNS resolved host name if available.

Previously, we were gathering this data only to include in the email copies of each new member and article submissions, but now we are databasing this information to be analyzed further in the future to prevent fraud or help us understand pattern abuse from authors who tag-team to game our system.

Thanks again for the suggestion. :-)

Comment provided August 12, 2005 at 11:24 AM

[Reply]

RSS feed for comments on this post.

Leave a comment

Please read our comment policy before commenting.