[Kevin]

I think you missed my point, Magi.

Dealing with cookie over writing and commission issues is one thing, and as far as the scope of the ABW community, the most important.

Like it or not though, since the FW toolbar and other USER INITIATED INSTALLS (and other forms of software marketing) are being utilized by shoppers for a specific purpose, my websites actions are an important part of the users shopping experience.

But I don't want to de-rail this thread. This would be a better discussion for this thread that I started, which didn't receive much input

[rematt]

Originally Posted by Kevin

Like it or not though, since the FW toolbar and other USER INITIATED INSTALLS (and other forms of software marketing) are being utilized by shoppers for a specific purpose, my websites actions are an important part of the users shopping experience.

The problem today is that any action we take against software affiliates puts the user right in the middle of the fray. Unfortunately accommodating that user also means giving a commission to the software affiliate and at the same time reinforces the users idea that "this is a good thing". We're going to have to battle software affiliates on multiple fronts and unfortunately the user will be affected also. I really don't think that attempting to educate the user will make a difference, they really don't care if I lose a commission as long as they benefit in some way. Hell, there are some that don't want us to make commissions whether they get something or not.

The problem that I see looming is that there will be a proliferation of different technologies developed that are all designed to divert commissions. It's apparent that the majority of networks don't care and that there are enough clueless merchants to make it very profitable and virtually risk free for the software affiliate. Perhaps the only way to compete is for all of us to have our own software solutions. Imagine that user experience.

But don't get me wrong. I do care about keeping my users happy. But let's be honest, I want them happy so that they will buy from a merchant that I recommend so I can earn a commission. If there is little or no prospect of earning a commission because that user has the technology from another affiliate installed in their browser, then I would much rather they experience another affiliates site. If enough of us utilize technology to fight technology and deny access to the information that shoppers need to make an informed purchase, then maybe the inconvenience of being denied access will get the users attention. Even if it doesn't, I'll be damned if I make a software affiliates wallet any fatter.

A simple statement like:

The technology installed in your browser in the form of _______ toolbar interferes with the contractual arrangement that this site has with one or more merchants featured on this site. In order to maintain the integrity of the contracts currently in place, your browser is being denied access to this site until such time as the specific technology is either disabled or removed.

We apologize for any inconvenience, if you have any questions please contact the supplier of the installed technology.

No shoes, no shirts, no service may be an inconvenience, but it works.

-rematt

[Haiko de Poel, Jr.]

An affiliate should always sell, I can't say it enough!!!

[Kevin]

Very true, H. That's the value we're supposed to be bringing to the merchants. Furthermore, since we're commissioned, it's the sole reason we do this.

[Kaitlyn2004]

Originally Posted by Magi

Take a look at parasite-data.js - that file has the list of whatever BHO back in 05 - ... this has changed greatly over the years ..

In Order to block out the BHO / Toolbar , you going to have to figure out the CSID and plug it in there ...

and to do that .. you have to install the toolbar, and search the Registery -

-----

I tried this with the AirMiles toolbar (got the clsid from registry), however it was not detected...

[2busy]

I tried this with the AirMiles toolbar (got the clsid from registry), however it was not detected...

If you installed the AirMiles Toolbar to test with you should be able to look at your access logs to see what user-agent (if any ) is showing up.

[Kaitlyn2004]

Originally Posted by 2busy

If you installed the AirMiles Toolbar to test with you should be able to look at your access logs to see what user-agent (if any ) is showing up.

It doesn't change the user agent

[Haiko de Poel, Jr.]

Right, You'll need to pull the airmiles' toolbar CLSID.

[Kaitlyn2004]

Originally Posted by Haiko de Poel, Jr.

Right, You'll need to pull the airmiles' toolbar CLSID.

The one I found was {DF4AE253-A021-47a9-BF12-01419785971C}, which did not seem to get detected... when I added it to the parasite-data..

[Georgie Peri]

If i ever get free time .. im going to setup a virtual client on my system to download and get most of the toolbar csids ..

and make more tests ! .....

but .. ugh im super busy