First let me say that I believe that anyone who submits galleries or runs a paysite and doesn't have some kind of hotlink protection is just begging for trouble. I don't have much sympathy for you when you get Fuskered. Having said that, I still believe what Fusker does is wrong and I am ready to do something about it.
If something irritates me, I like to try to find an innovative way to deal with it. I have effictively shut down a few medium-sized phishers by writing a little script that connects to their script via a proxy and submits false information over & over again so they are flooded with bogus customer data. Even if someone is stupid enough to give the phishers their actual login information, the phisher will more than likely never see it due to the tremendous amount of bogus data I have sent them. This is particularly effective when there is more than one person running the script...but I digress.
I was thinking about the Fusker problem today and was trying to figure out a legal but effective way to deal with it. Here's what I came up with:
I can write a script that will connect to Fusker every 30 minutes or so and check all of the newest "Fuskers" that are listed. When the script finds one that has working images, the script will do a quick whois on the domain and send the owner of the domain an email explaining what Fusker is and how to stop it from stealing their bandwidth. There will obviously have to be a lot more to it, but that's my basic idea. If anyone (especially other programmers) have any ideas on how to improve upon this, please let me know.
If something irritates me, I like to try to find an innovative way to deal with it. I have effictively shut down a few medium-sized phishers by writing a little script that connects to their script via a proxy and submits false information over & over again so they are flooded with bogus customer data. Even if someone is stupid enough to give the phishers their actual login information, the phisher will more than likely never see it due to the tremendous amount of bogus data I have sent them. This is particularly effective when there is more than one person running the script...but I digress.
I was thinking about the Fusker problem today and was trying to figure out a legal but effective way to deal with it. Here's what I came up with:
I can write a script that will connect to Fusker every 30 minutes or so and check all of the newest "Fuskers" that are listed. When the script finds one that has working images, the script will do a quick whois on the domain and send the owner of the domain an email explaining what Fusker is and how to stop it from stealing their bandwidth. There will obviously have to be a lot more to it, but that's my basic idea. If anyone (especially other programmers) have any ideas on how to improve upon this, please let me know.
Comment