Quote:
|
Originally Posted by Sly
I'm curious...
If a surfer forum was linking to a movie you have on your server and it ran up your BW bill, I'm sure you would take immediate action to block them or "seek revenge". Would you not? So let's assume you put up a ******* video on your server. Its your server, you can put up whatever legal material you want, right? Well, this surfer forum doesn't like ******* near as much as GFY does, so they email your host complaining about your totally legal movie instead of taking action and correcting their wrong doing. Your host, for whatever reason, agrees with the surfer forum and they pull down your legal video without saying boo to you.
How would you respond? The surfer forum has a right to change legal content on YOUR server?
|
You, I will come back and respond to since you are not name calling and actually want to exchange opinions.
I think we all know that once a webhost has been notified of questionable behavior, the webhost 99% of the time is going to take action. GFY is quick to notify them of content thief's, and it is expected that the site will be removed in short order even though the webhost has nothing to do with the site itself.
In your example above, as you said, there is nothing illegal going on. I would not expect a webhost to remove content in a scenario you have described. I would be VERY upset if they did.
Let me use this example though...
Sly, lets say you run the largest surfer forum in the world (that is supposed to be family friendly) and some of your surfers hotlink a flash video from me to go in their posts. I know the hotlinking is taking place, but I don't implement .htaccess or even contact you to put a stop to what your members are doing. Instead, I modify the file to pop an XXX ad on your family friendly forum.
You, of course being the largest forum in the world, don't want to take on the massive burden of relying on your software (and the extra needed hardware) to filter out all of the people attempting to do stuff like this (nor do you want to become a SPAM hotbed for porn sites), so you nip this in the bud and go to my webhost. Right?
Well there I am, left with a hosting bill because of what your surfers started. In the end, all I had to do was implement .htaccess or contact you instead of letting it blow up into something it shouldn't have after taking justice into my own hands. Right?