:glugglug

If there is a submit page on Huns webmaster area for new leecher IPs, as soon as a webmaster sees new leeching, he can go to Huns webmaster area, submit the new ip, and people can update their .htaccess file.

they realize they just don't care. img scr them fight fire with fire

Img src their host and see how long their site lasts.

Agreed.. :glugglug

i for one vote to take them down the hard way... that way they can get a nice BW bill to help them remember to stop fucking us and stealing our BW!!

i know 2 wrongs doesnt make 1 right, but sometimes you just need to say "fuck it" and do things the dirty way to get your point across!

The site and program have been DOA for some time now. I just hadn't taken it offline. Out of respect for The Hun, and other hardworking webmasters, the program and site are no longer available. ThumbGal was done at a time when I was new to Internet porn. I didn't properly think about it's ramifications and once I did, I stopped promoting the site/software and just let it die a slow death. It's completely dead now, and now I move on to other ventures in the online porn realm.
Good day.

Thank you for finally closing the site! When I looked this morning, it was still up.

picleecher (250,000 pageviews/day) will be taken down soon probably. I think it's only a matter of time now (judging from the host's answer).

Thank you, well appreciated!

Fusker! is dead. Long live fusker.
Fusker.com will no longer be hosting the Fusker! web extractor. However, we have decided to make a version of the code available to all users. If you would like to host your own fusker using our code, just click here. For more information about this software click here. Once you have your fusker up and running let us know and we'll give you a link.


good work..:glugglug

okay, picleecher seems to be off now.

I'm not sure if it was the host that took it down though since they haven't responded about that specifically yet

LOL that guy is an asshole, ive never read so much crap in my life. :1orglaugh

you mean the fusker guy?

good those fuckers have been makin my error logs look like shit for a while now

I love when TheHun turns his attention on a vexing problem like this and suddenly things just start to happen!!!!

What are the other major Leecher programs out there that need to be dealt with?

http://picleecher.com/

Bandwidth Limit Exceeded
The server is temporarily unable to service your request due to the site owner reaching his/her bandwidth limit. Please try again later.


:glugglug :thumbsup

I've done a quick look at it, and it seems that they are just ordinary hotlinking the images.

A little thought about it, and i've come up with this easy quick and dirty solution:

If you're building a gallery, do it like this:

domain.com/galleryXXX/images/
domain.com/galleryXXX/thumbs/
domain.com/galleryXXX/graphics/
domain.com/galleryXXX/index.html

In the /images/ directory put an htaccess file with this:

RewriteEngine on
RewriteOptions inherit
RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{HTTP_REFERER} !^http://.*domain.com/.*$ [NC]
RewriteRule .*[Jj][Pp][Gg]$|.*[Gg][Ii][Ff]$ http://www.domain-redirect.com

Change the domain.com etc. Should work out just fine, but this is just a temporary solution.

A better solution would be something like a central blocklist of ip's that can be updated by every webmaster out here. But that will require a little bit more programming though :winkwink:

The site is Error 500 here

one thing I do if I'm not bothering with htaccess is to randomly name the files.

These leech sites use a numbering system to easily pull your pics, like 1-50 and such... if you're namimg the pics in a random way, it's too much of a pain in the ass for them to link hotten you.


Oh, the fusker guy was on GFY a few days back:
http://www.gofuckyourself.com/showth...hreadid=216204

I had a problem with the original developer of fusker. At least I'm glad to see that the take-offs are at least being sensitive to the email inquiries. The original guy ignored me, as well as their host.

I wrote an article a while back on how to find the hosts for certain sites, it's still available at -

http://ynotnews.ynotmasters.com/issu...402/page5.html

Just like password sharing sites, stamp one out, 2 more appear.

David
webmaster
greatgirls.com

It could be simply solved by sumbmitters. But then you would have to approve that the image source is done through php something like < i m g s r c = p i c . p h p ? 1 5 >
for example. This would block all the freeloaders. But i presume this wont be an option.

second
When will you post your blacklist again...so we can update to. Have send you some mails about it.

i say img src his ass. this is no different then hacking our servers and putting his banners in place of ours. i forgot to put htaccess on one of my domains for a day and he burned about 50 gigs of my bandwidth before i realized and put the htaccess up. if you need any help just let me know.

Someone brought this up a while ago and I believe it would work.

1) Create an .htaccess in your images directory that redirects all hotlinks to a password protected page

2) Have the .htaccess set up so the "authorization failed" page redirects to the page of your choice. It could be a sponsor, or a page saying that the site you are viewing is under investigation for the mass pirating of adult content and their IP has been logged (he he he...)

So when they don't have a password IE *SHOULD* redirect them to the page in the .htaccess. I haven't tried it but I'm pretty sure it'd work.

Since the guy who runs Fusker doesn't seem to understand why his shit is a problem.. Maybe the next time you email him you should explain that what he is doing is called "theft of services". That it would be no different than him running an extension cord over to his neighbors house, plugging into an outside outlet and then powering his house while his neighbor pays the bill.

Sometimes you need to paint the slow people a picture they can understand. ;)

Those and the spamfreeforums guys suck alot of bandwidth.
They hotlinked some large movies off my server and were pulling 80mb/sec for a couple hours nonstop. Had to remove the files :(

*bump*

Interesting thread, I'm going to hunt through my log files right now...

The (recent?) fusker 'feature' of indiscriminately hotlinking a numbered range of images caused a lot of problems on one of my sites, because they img src'd a php script rather than the images which it displays. The end result: 250+ rapid-fire loads of a PHP script within a few seconds by each fusker surfer. Some of them even reloaded since all of the images showed as broken.

One quick fix for fusker dumbasses who try to hotlink HTML scripts rather than images might be to check the http_accept variable - if the browser is expecting an image rather than HTML then abort the script (or 302 to a suitable 'fuck you' image :) )