Forum Moderators: open
p.s. Or should I pay 4$ and ask Google answers?
More generally, there are a few packages designed to do this sort of work, but they are really aimed at massive (100,000+ images) libraries, the Corbis's of this world. The prices are enterprise scale too
I had a look around, and there is very little in the lower end of the market, once you get away from Photo Album type software, which simply helps to organise images, but does nothing for security etc
Depending on how you are set up with your server, you could have it deliver different images depending on who is asking (ie if you spot someone stealing your images, future requests from that IP/range get an image with "These guys are rip-off merchants!" or something)
Thats why you use watermarking. Any image displayed on the Web is lowish res, and has a damn great copyright notice over it, noting the source domain
Some packages do it on the fly, otherwise you have to pre-process the images before releasing them to the Web. Sharp eyes are the best defence really though. Sad that it has to be reactive, not proactive, but the Web is based on trust, which is sometimes abused. *shrug*
Ultimately, it was just a little misdirection. It still didn't prevent me...er...anyone from obtaining the image, but it was pretty creative.
-Elliott
You can also erect some defenses like htaccess preventing other web sites from poaching images [webmasterworld.com], disable right-click, etc.
Josh
(*doh* Didn't even think of grabbing a screenshot though. That would work fine for my needs...)
Using a proprietory data format for display (requiring the plug-in) is a stronger line of defence, but its kind of hard to make it work for general surfers. Some are so paranoid they won't d/l Flash, because they think it'll do strange and terrible things to their machine. Even if there is some kind of trick in there to disable the "print screen" method, with the right gear you can just tap it straight off the monitor feed.
Ultimately, all of these methods are aimed at protecting your own images by making it easier to steal someone elses, and for the moment, thats about as good as you get.
<head>
<meta http-equiv=Pragma content=no-cache>
<META HTTP-EQUIV="imagetoolbar" CONTENT="no">
<meta http-equiv=expires content=0>
<script language="JavaScript">
//Copyrighted Image Protector 2 Version 1.1
//functionality developed by winffb.com/logos 2000-2002
function nocontextmenu()
{
event.cancelBubble = true
event.returnValue = false;
return false;
}
function norightclick(e)
{
if (window.Event)
{
if (e.which == 2 ¦¦ e.which == 3)
return false;
}
else
if (event.button == 2 ¦¦ event.button == 3)
{
event.cancelBubble = true
event.returnValue = false;
return false;
}
}
if (document.layers) {
document.captureEvents(Event.MOUSEDOWN);
}
document.oncontextmenu = nocontextmenu;
document.onmousedown = norightclick;
document.onmouseup = norightclick;
//-->
</script>
</head><body OnLoad=trap()></body>
I call the image from a smaller file using Java Script so the person visiting the larger image must have their browser Java Script enabled. This function basically disables all caching/history problems. Any right click features, and it disables the IE 6 image toolbar. Weaknesses include (but are not limited to) "pulling" the image into the address bar. I fix this by popping the image into its own window that doesn't display the address bar. It can still be abused though. Also, as stated above. Screen captures trump all. If they can see it, they can steal it.
As you said the user may not be able to steal the image directly.
But all the jpg,gifs goes into the user's cache memory so he can easily use it.
another method of image stealing is print screen (image capture).
Flash images can be protected. But it can also be captured using print screen.
So no method is 100% fool proof to stop image stealing.
-Suresh Babu
When someone tried to copy the jpeg, they got only the clear gif. Don't remember the details.
But that's no help for screen dumps or recovery from the client's cache.
DigiMarc is pretty expensive, but (last I looked) they offer a service for tracking your watermarks around the web for you.
Watermarks like DigiMarc also don't fit into the smaller graphics files (jpeg image had to be over approximately 250px to 300px square) and can corrupt image files that are nearly too small for them to fit into.
Some image databases (ThumbsPlus) recognize watermarks and let you work with them, some do not.
Save Me! [home.earthlink.net]
This my help against the AVERAGE user.
Every little bit helps!
-Marty
The point of the table is to make it difficult to save the image utilizing the browser.
The "average" user is not going to dive into the source code to extract an image file name.
When you try to save this image using the browser, all you get is a blank image.
We ALL know that their is virtually NO way to stop a determined person from snatching an image. All we can do is make it a little bit harder.
Like I said:
1. This may help against the AVERAGE user.
2. Every little bit helps!
-Marty
P.S. I've found that the best defense is posting ugly overly-compressed .jpg images (overexposed or blurry images are especially safe) ;)
That is the whole sure fire way to protect your images. Sometype of program that does not register with the clip board. But Netscape and non-IE browsers will not be able to view it.
Search Google for the program, I am sure you can find it.
I was talking about Clever Content 2.0, Although it looks like it was discontinued and renamed Mirage 2.0.
http://www.alchemedia.com/support/ccvsmirage.html