I've even put anti-hotlinking code into web sites. All they would get
would be some silly graphic saying to not to hot link. Back in the
time when bandwidth on a server was expensive this was important. Not so
much that someone on a group like Yahoo might post a link to your image
but a malcontent might create a script kiddie to run up your bandwidth
use. I probably got some kid thrown out of college for that on my
Earthlink site. He ran up about 14 GB of overrun but Eathlink could see
it was coming from a server at a college during winter break. That
overrun could have cost $600.
Nowadays most web hosts offer unlimited bandwidth... cheap. However you
can still get malcontents create DOS scripts. If a few of them were
shot then that might cool the fun for the rest of them. ;-)
On 09/26/2013 07:27 AM, j_alexander_stan...@yahoo.com wrote:
At the risk of adding more confusion than clarity, I will point out
that there's also the issue of some servers not allowing off-site
hotlinking. If you find an image to embed with the same browser that
you use to post, the image can show up in preview and on the FFL
website FOR YOU but no one else because the search for the image put
it in your browser cache, and it will display FOR YOU regardless of
the site's hotlinking policy. However, if the server hosting the
embedded image doesn't allow hotlinking, the image will not display
for anyone else. That's why I always recommend doing image searches in
a different browser than the one you post with; that way, the image
isn't in the FFL posting browser's cache, and previewing the embedded
image will reveal if hotlinking is not allowed.
That said, Barry's right. Assume Yahoo is completely fooqued up and
post a link to the image as well.
