Comments on: Alexa Network: Cooperative Exploit. http://money.bigbucksblogger.com/alexa-network-cooperative-exploit/ Comments on blogs about making money blogging. Thu, 18 Mar 2010 14:28:25 -0700 http://wordpress.org/?v=2.8.6 hourly 1 By: Alexa Game: You Visit, I Visit : Big Bucks Blogger http://money.bigbucksblogger.com/alexa-network-cooperative-exploit/comment-page-1/#comment-1612 Alexa Game: You Visit, I Visit : Big Bucks Blogger Fri, 31 Aug 2007 19:38:59 +0000 http://money.bigbucksblogger.com/alexa-network-cooperative-exploit/#comment-1612 [...] Install the Alexa toolbar. (This is absolutely required or no one will get an Alexa boost. To read why, visit Alexa, cooperative exploit. [...] [...] Install the Alexa toolbar. (This is absolutely required or no one will get an Alexa boost. To read why, visit Alexa, cooperative exploit. [...]

]]> By: Lucia http://money.bigbucksblogger.com/alexa-network-cooperative-exploit/comment-page-1/#comment-1473 Lucia Tue, 28 Aug 2007 21:06:44 +0000 http://money.bigbucksblogger.com/alexa-network-cooperative-exploit/#comment-1473 I've seen centralized systems like you describe, but I haven't seem one with the feature where they detect who you are so that you only get visits if you visit. Using a plugin makes it decentralized and will tend to make things look a bit more "natural". (Though, I think the Alexa toolbar has so very little "intelligence" that natural vs. unnatural isn't much of a problem.) I did some coding to prevent any one person from visiting the same site too many times in a row. Visiting from one IP address two or three times in a day is ok, but visiting the same blog 100 times is just a waste of time for everyone in "the project". The coding is simple but the exact "rules" are too long to describe in a comment. I'm looking for volunteers to email me to test this out. If it doesn't have glitches, I'll release, and then I'll describe in more detail. I’ve seen centralized systems like you describe, but I haven’t seem one with the feature where they detect who you are so that you only get visits if you visit.

Using a plugin makes it decentralized and will tend to make things look a bit more “natural”. (Though, I think the Alexa toolbar has so very little “intelligence” that natural vs. unnatural isn’t much of a problem.)

I did some coding to prevent any one person from visiting the same site too many times in a row. Visiting from one IP address two or three times in a day is ok, but visiting the same blog 100 times is just a waste of time for everyone in “the project”.

The coding is simple but the exact “rules” are too long to describe in a comment. I’m looking for volunteers to email me to test this out. If it doesn’t have glitches, I’ll release, and then I’ll describe in more detail.

]]> By: Lord Matt http://money.bigbucksblogger.com/alexa-network-cooperative-exploit/comment-page-1/#comment-1472 Lord Matt Tue, 28 Aug 2007 20:47:27 +0000 http://money.bigbucksblogger.com/alexa-network-cooperative-exploit/#comment-1472 Interesting plan. My method was the frame loaded (by redirect) page system. I've been resting it while I fight of a DDoS (not a geat one and possibly not totally diliberate but spammy and bad nonetheless) on the server. I used to run a traffic exchange years ago and have some open source code (it's not that good) from those days. It uses what might be described as some sorta rolling matrix of clicks. You fill out your site and pay off the guys already int he system by vsiting thier framed pages and giving the rank and this buys you into the system int he same way. This way you get out what you put in but you have to do it daily to get the most out. Unlike you I have a feature left to code - stopping a person from looking fromt he same IP at the same site twice in one day. That needs an extra data table and I'm not done with that. Int heory multiple exchanges could be run with trafficshared among exchanges for a more "random" bell curve distribution via a basic API. However, your idea has me interested too. Interesting plan. My method was the frame loaded (by redirect) page system. I’ve been resting it while I fight of a DDoS (not a geat one and possibly not totally diliberate but spammy and bad nonetheless) on the server. I used to run a traffic exchange years ago and have some open source code (it’s not that good) from those days. It uses what might be described as some sorta rolling matrix of clicks. You fill out your site and pay off the guys already int he system by vsiting thier framed pages and giving the rank and this buys you into the system int he same way.

This way you get out what you put in but you have to do it daily to get the most out.

Unlike you I have a feature left to code – stopping a person from looking fromt he same IP at the same site twice in one day. That needs an extra data table and I’m not done with that.

Int heory multiple exchanges could be run with trafficshared among exchanges for a more “random” bell curve distribution via a basic API.

However, your idea has me interested too.

]]>