Quote:
Originally Posted by pompousjohn
Anybody who really wants to shave can shave. The method you described above is far more complex than a number of easier options I can think of right now. I don't think anyone who was into shaving would do it that way. I think most people would alter the database directly from the backend or else have a script that redirected incoming hits to an in-house affiliate account by overwriting the cookie at either a timed or percentage based interval.
There is no point in shaving on a per transaction basis, as in joins but not rebills, it has to be per customer in order to be effective. Otherwise there will be mismatched rebills and refunds as we are seeing here and the community will be alerted shortly.
|
Yes but you see In theory if someone can manually toggle the options between say noon and 8pm and escape detection then they can also automate it and do it in other ways such as with cron entries executing scripts at certain times which modify the database or configuration files. It would be pretty easy in fact-- if that is possible and evidence is not shown to the affiliate of it occurring by NATS.
Also if rebills tend to come in at certain times from a certain processor it might in theory be used to easily shave rebills too by selectively turning on and off various options. You would turn it off right before the rebills tend to come in and turn it back on right after. But again it all depends on how NATS displays this along with the retro active and hide options.