GoFuckYourself.com - Adult Webmaster Forum - View Single Post - Possible New Toolbar Problem Targeting Traffic Scripts

Fuckin Bill · 06-28-2007, 01:38 PM

I have an idea for a possible solution. I think it would stop this toolbar and anything similar in the future.

The flaw in the system (any tgp system) is the forwarding redirect from the TGP script, to the traffic script. If that redirect were eliminated, there's nothing for a program like this to catch and modify, assuming that the gallery url is not passed along during clicks.

If a traffic script had a version of their out script that could be included into another php script (the tgp out script) that final redirect could be eliminated. I think it would just take a little extra work on the part of the TGP script guys, and the traffic script guys.

On the trafic script side, you have the out script encapsulated in a function. Pass the variables to the function, instead of through a url. Something like this.

Code:

trafficout($skim, $url, $linktag);

On the tgp script side, you ask in the config/settings, where is the traffic script to be included, and what is the format of the function to call it. Then in the "out" script for the tgp software, you just add an IF statement at the very end where it would normally hand off the redirect to the traffic script:

Code:

if !$trafficinclude {Run normal routine and redirect externally} else {include $trafficinclude; trafficout($skim, $url, $linktag);}

This would still work (I think) even with zend encoding on both sides, so nobody would have to give up their source, and things would be modular and could work together with no holes in the middle. The traffic script would still be able to run with full access to the system variables if it needs them, and would have correct IP address and cookies and everything.

But now, the surfer would click, the tgp script would do it's thing, the traffic script would do it's thing, and then a simple single URL is spit out as a redirect. Anything (like this toolbar) sitting in the middle would not know anything about the gallery until that final redirect is sent, and then it wouldn't know if the URL being put out is the gallery, or a trade, because it has nothing to match it to, and it never saw any variables passed to the traffic script through the url.

I don't think this would really cause more than a few minutes work for programmers on either side, and although I'm not sure, I'm guessing the scripts written in C could also have a small php wrapper written that would allow them to be included into a php script.

06-28-2007, 01:38 PM
Fuckin Bill Confirmed User Join Date: Feb 2003 Posts: 1,020	I have an idea for a possible solution. I think it would stop this toolbar and anything similar in the future. The flaw in the system (any tgp system) is the forwarding redirect from the TGP script, to the traffic script. If that redirect were eliminated, there's nothing for a program like this to catch and modify, assuming that the gallery url is not passed along during clicks. If a traffic script had a version of their out script that could be included into another php script (the tgp out script) that final redirect could be eliminated. I think it would just take a little extra work on the part of the TGP script guys, and the traffic script guys. On the trafic script side, you have the out script encapsulated in a function. Pass the variables to the function, instead of through a url. Something like this. Code: trafficout($skim, $url, $linktag); On the tgp script side, you ask in the config/settings, where is the traffic script to be included, and what is the format of the function to call it. Then in the "out" script for the tgp software, you just add an IF statement at the very end where it would normally hand off the redirect to the traffic script: Code: if !$trafficinclude {Run normal routine and redirect externally} else {include $trafficinclude; trafficout($skim, $url, $linktag);} This would still work (I think) even with zend encoding on both sides, so nobody would have to give up their source, and things would be modular and could work together with no holes in the middle. The traffic script would still be able to run with full access to the system variables if it needs them, and would have correct IP address and cookies and everything. But now, the surfer would click, the tgp script would do it's thing, the traffic script would do it's thing, and then a simple single URL is spit out as a redirect. Anything (like this toolbar) sitting in the middle would not know anything about the gallery until that final redirect is sent, and then it wouldn't know if the URL being put out is the gallery, or a trade, because it has nothing to match it to, and it never saw any variables passed to the traffic script through the url. I don't think this would really cause more than a few minutes work for programmers on either side, and although I'm not sure, I'm guessing the scripts written in C could also have a small php wrapper written that would allow them to be included into a php script.