Warning: Playing devil's advocate.
Flames, if any, can be dealt with in private.
I don't think this type of protection is the way to go. Of
course you can even write a small applet that will hide the
URL (for example) to stop people from downloading your files...
But this is a PAIN for people who come accross an image
and just want to keep them on their hard disks.
Plus it's so easy to circumvent and only end up making
the people visiting your site angry because they have to go
looking through all the ms426534216.jpg files in their temp
folder before they click anything that could clear their
cache.
The URL embossing is also a bit much. Most people who
download the images just think they are beautiful, will
stick them in their temp folder, and in a few months delete
them when they need extra disk space. It's a long and tedious
process to edit out such embossed URLs.
If you put something on the web, you're putting it in PUBLIC
domain. Most people are considerate and will e-mail you to
borrow pics, as they often did to me. They will link back
to you and often this will give you more traffic. Beneficial
transaction for both parties.
So there are a few bad apples, no need to ruin everything
for the others.
The only thing I abhor is cross-linking.
|
