Kill xites.com!

[SunTzu]

Somone posted a link to their site using this as well. This will also work to break you out of someone's frames. If we ALL use it, xites will go away.


<script language="JavaScript">
<!--
var me = "http://www.yourdomain.com/";
if (self.location != me) {
self.location = me;
}
if (self != top) {
top.location = self.location;
}
// -->
</script>

xites!

[SunTzu]

oops, the code! put this in jscript tags of course..

var me = "http://www.yourdomain.com/";
if (self.location != me) {
self.location = me;
}
if (self != top) {
top.location = self.location;
}

[bawdy]

yeah good idea for sites

wont work for galleries cause at lot of TGPs will reject galleries with javascript.

why isnt htaccess a simple enough solution to prevent xsites hotlinking your content?

[foe]

just img src them

[bawdy]

Originally posted by SunTzu
oops, the code! put this in jscript tags of course..

var me = "http://www.yourdomain.com/";
if (self.location != me) {
self.location = me;
}
if (self != top) {
top.location = self.location;
}

oh yeah how long do you reckon it will be before xites strips any javascript from your pages with self.location in them?

[SunTzu]

Fine, lets make it a .js file then.. If enough sites do this, it won't be worth their time.

[Fatbrain]

Bad thing is that will break you out of translation sites such as babel fish

But, if your sales are decently dependent on overseas sales, then it wouldn't be a big deal...But that isn't an option for me as about half of my sales come from Europe and Asia.

We could just hire someone to shoot em! =P~

[DragonAss]

Originally posted by bawdy
why isnt htaccess a simple enough solution to prevent xsites hotlinking your content?

.htaccess will work. The only problem is that you need to know which site(s) to block. If the xq1.net site feels too many are blocking them, they could just move to xq2.net or wherever.

I'm trying to think of a "hands off" approach to dealing with new sites as they pop up. The way things stand now, this PHP script isn't that big of a deal so long as any external access to your pics is blocked.

The worst case scenario is they work around that block. It would cost them some bandwidth to do so... but it can be done. In this case then, it's mostly a copyright issue plus the fact that they're still pulling the data from your server and making money by altering your links. Not cool IMHO.

Luckily surfing via that crap tends to suck ass and surfers can't be happy campers for too long.

[Alky]

Originally posted by DragonAss
.htaccess will work. The only problem is that you need to know which site(s) to block. If the xq1.net site feels too many are blocking them, they could just move to xq2.net or wherever.

I'm trying to think of a "hands off" approach to dealing with new sites as they pop up. The way things stand now, this PHP script isn't that big of a deal so long as any external access to your pics is blocked.

The worst case scenario is they work around that block. It would cost them some bandwidth to do so... but it can be done. In this case then, it's mostly a copyright issue plus the fact that they're still pulling the data from your server and making money by altering your links. Not cool IMHO.

Luckily surfing via that crap tends to suck ass and surfers can't be happy campers for too long.

they could easily use a proxy in the perl script that fetches the webpage.

[Pipecrew]

The Hun is so going to crack down on this, just watch just like gator.....

the minute a visitor complains to him about seeing a banner on his page....... I am willing to bet any ammount

[skazzel]

The thing is, it's fairly trivial to code something like this up:

http://198.92.101.168/xit/xit.php?xi...ww.google.com/

This took me about two days and 250 lines of code to write - it isn't 100%, but it renders many sites better than xites.

I implemented two ways of fetching images, direct and passthru. The direct method rewrites the img tags to point directly at the image on the server. This means the image loading is not being done through the xit proxy or using your bandwidth. Unfortunately, anti-hotlinking .htaccess files will break this, as it looks like the images are being hotlinked. The passthru method is what xites does, but my script also fixes the referer(sic) header so sites with the anti-hotlinking .htaccess still load.

[HQ]

Originally posted by skazzel
The thing is, it's fairly trivial to code something like this up:

http://198.92.101.168/xit/xit.php?xi...ww.google.com/

This took me about two days and 250 lines of code to write - it isn't 100%, but it renders many sites better than xites.

I implemented two ways of fetching images, direct and passthru. The direct method rewrites the img tags to point directly at the image on the server. This means the image loading is not being done through the xit proxy or using your bandwidth. Unfortunately, anti-hotlinking .htaccess files will break this, as it looks like the images are being hotlinked. The passthru method is what xites does, but my script also fixes the referer(sic) header so sites with the anti-hotlinking .htaccess still load.

Nice coding anyway, skazzel.

[Juge]

Originally posted by SunTzu
Somone posted a link to their site using this as well. This will also work to break you out of someone's frames. If we ALL use it, xites will go away.

xites!

This code should be used anyway. Why allow anyone to open your site in one of their frames? It also helps break out of the google image search, as well.

[skazzel]

Originally posted by HQ


Nice coding anyway, skazzel.

Thanks HQ,

If you or anyone is looking for someone reliable to do custom programming work, I'm currently looking for gigs.