hellboy
07-03-2009, 11:58 AM
Where can I find ready-to-use solution to realize this feature:
user clicks on Save Image as.
Original image is not saved, but stub image
user clicks on Save Image as.
Original image is not saved, but stub image
Click to See Complete Forum and Search --> : Image protection against download
tedscoffee
07-06-2009, 07:36 PM
You can try to use some flash photo gallery (http://gallery.a4desk.com) to display your images instead -- as right click does not work with Flash. However you should note they can still steal you images by using screen captures.
hellboy
07-07-2009, 05:15 AM
Thank you.
I think this is the only way to create "protected" images.
HTML images are stored in cache and can be easy restored from cache (image file and URL of image)
I think this is the only way to create "protected" images.
HTML images are stored in cache and can be easy restored from cache (image file and URL of image)
Valerie8
04-11-2011, 08:07 AM
I also know that there're some galleries that block right mouse button and download function is disabled...
Kor
04-11-2011, 08:26 AM
I also know that there're some galleries that block right mouse button and download function is disabled...
It's of no use. The user might disable javascript. Or it might simply use the View Source to analyze the code and to see which is the image's address. Or even more simpler: Print Screen.
The only reliable protection is to spread a watermark over your picture.
It's of no use. The user might disable javascript. Or it might simply use the View Source to analyze the code and to see which is the image's address. Or even more simpler: Print Screen.
The only reliable protection is to spread a watermark over your picture.
coldfire421
04-11-2011, 11:53 AM
There is no actual solution for protecting image from a web to copy or download, even if you disable right clicking or put a script to prompt an alert when you click image. the user could only press the print screen on their keyboard presto they already stole your photos.
watermark is good but some good in graphics can only fix and remove it using some graphics application like photoshop. I my self can do that but of course I didnt do it LOL
watermark is good but some good in graphics can only fix and remove it using some graphics application like photoshop. I my self can do that but of course I didnt do it LOL
Kor
04-11-2011, 12:36 PM
T
watermark is good but some good in graphics can only fix and remove it using some graphics application like photoshop. I my self can do that but of course I didnt do it LOL
Which of course you did. Like all of us :D
watermark is good but some good in graphics can only fix and remove it using some graphics application like photoshop. I my self can do that but of course I didnt do it LOL
Which of course you did. Like all of us :D
skilled1
04-18-2011, 05:18 PM
if you have an anti-right click script firefox plugin noscript will block it.
if you imbed it in flash i can still take a screenshot
if you watermark it i can clonestamp anything and put it to where 99% could never tell
if you place it on your page as a background of a table with a transparent image over it i can rip though your page and still steal the image.
no matter what you can do, just assume that if someone wants the information / image they are going to get it.
if you imbed it in flash i can still take a screenshot
if you watermark it i can clonestamp anything and put it to where 99% could never tell
if you place it on your page as a background of a table with a transparent image over it i can rip though your page and still steal the image.
no matter what you can do, just assume that if someone wants the information / image they are going to get it.
Valerie8
04-19-2011, 02:37 AM
if you place it on your page as a background of a table with a transparent image over it i can rip though your page and still steal the image.
Never knew about this..you say it's possible it makes me upset... Is it easy to do?
Never knew about this..you say it's possible it makes me upset... Is it easy to do?
skilled1
04-19-2011, 09:41 AM
Never knew about this..you say it's possible it makes me upset... Is it easy to do?
very easy, create a table without cell padding or cell spacing and give the table the same width and height as the dimensions of your image you are trying to protect, then set the table background to the image you want.
then create a 1px by 1px transparent gif.
then in the <td> of the table you already created, place the gif you create and give it the same width and height as the image you are trying to protect.
this will make it so if someone trys to right click with say the firefox plugin noscript, all they are able to save is the 1x1 gif. this however will still not protect against a screenshot.
very easy, create a table without cell padding or cell spacing and give the table the same width and height as the dimensions of your image you are trying to protect, then set the table background to the image you want.
then create a 1px by 1px transparent gif.
then in the <td> of the table you already created, place the gif you create and give it the same width and height as the image you are trying to protect.
this will make it so if someone trys to right click with say the firefox plugin noscript, all they are able to save is the 1x1 gif. this however will still not protect against a screenshot.
svidgen
04-19-2011, 10:16 AM
My policy on asset protection always involves a statement like this:
If the image were on paper, someone could reproduce it by scanning and color-correcting it in about 5 minutes. If you can make someone jump through about 5 minutes worth of hoops to steal your asset, you're probably doing as much as you can. If you can make it take longer -- that's awesome. But, don't fret over it. Your stuff isn't that original anyway.
As I see Kor suggest over and over on this topic, a better form of protection is usually just some form of image degradation, like a watermark or an unobtrusive copyright mark that isn't worth the effort to remove and either leads folks back to your site or allows you to prosecute the thief.
Though, I highly recommend against prosecuting image thieves in most cases.
The exceptions would be for paid content, wherein the user agreed to a license before accessing the images. And in those cases, it's still best not to put so much effort into preventing theft, but to find some way to track theft. You might track suspicious behavior (right clicks, etc.) and go after folks who's interactions are highly suspect. Or you might find it best to mark each image with the requester's IP and a time-stamp (in a small, subtle way -- discolored pixels or something). Then, if you see your images in the wild, you can determine who stole them and when.
But again, the cases wherein image "theft" is really a bad or serious thing should be pretty minimal. You're kind of a "bad guy" if you go over the top with it. Whereas you're a "good guy" if you just let it happen. And, as long as you're letting it happen, for images that you put a lot of sweat and blood into, you can easily toss a (c) yoursite.com near the bottom -- "free" advertising!
If the image were on paper, someone could reproduce it by scanning and color-correcting it in about 5 minutes. If you can make someone jump through about 5 minutes worth of hoops to steal your asset, you're probably doing as much as you can. If you can make it take longer -- that's awesome. But, don't fret over it. Your stuff isn't that original anyway.
As I see Kor suggest over and over on this topic, a better form of protection is usually just some form of image degradation, like a watermark or an unobtrusive copyright mark that isn't worth the effort to remove and either leads folks back to your site or allows you to prosecute the thief.
Though, I highly recommend against prosecuting image thieves in most cases.
The exceptions would be for paid content, wherein the user agreed to a license before accessing the images. And in those cases, it's still best not to put so much effort into preventing theft, but to find some way to track theft. You might track suspicious behavior (right clicks, etc.) and go after folks who's interactions are highly suspect. Or you might find it best to mark each image with the requester's IP and a time-stamp (in a small, subtle way -- discolored pixels or something). Then, if you see your images in the wild, you can determine who stole them and when.
But again, the cases wherein image "theft" is really a bad or serious thing should be pretty minimal. You're kind of a "bad guy" if you go over the top with it. Whereas you're a "good guy" if you just let it happen. And, as long as you're letting it happen, for images that you put a lot of sweat and blood into, you can easily toss a (c) yoursite.com near the bottom -- "free" advertising!
Kor
04-19-2011, 11:52 AM
After all, Web supposes to be a free space, more or less. The moment you published something on Web, you have already lost a lot of power regarding your product.
coldfire421
04-20-2011, 10:29 AM
Yea that's the fact you should know, even if you made all your programming skills just to avoid other people to steal your pics. I will just grab my digital cam and take a shot on my monitor LOL.
Donny Bahama
04-20-2011, 12:17 PM
Never knew about this..you say it's possible it makes me upset... Is it easy to do?You don't even need the table to do this.
This is the method I use (when I bother to use anything)... Create two 1x1 gifs - one clear, the other a solid color. (I use #0f0.) Size it to match or exceed the size of your content div. Place it in a div at the end of (but within) your wrapper div so that it sits on top. During development, use green.gif. Load the page, make sure it's nothing but bright green, then edit the source, changing "green.gif" to "clear.gif" - voila!
This is good because it requires no javascript trickery which is easily disabled. When the user right-clicks and saves the image, he gets a 1x1 transparent gif. The downside, as mentioned, is that if the user really wants it, he can pull it from his cache or view the source. Viewing the source can be discouraged using document.write(unescape("%3c%69%6d%67%20%73%72%63%3d%22%72%65%61%6c%69%6d%61%67%65%2e%70%6e%67%22%3e")); but that's not exactly foolproof, either. If the user wants the image, there's always a way.
This is the method I use (when I bother to use anything)... Create two 1x1 gifs - one clear, the other a solid color. (I use #0f0.) Size it to match or exceed the size of your content div. Place it in a div at the end of (but within) your wrapper div so that it sits on top. During development, use green.gif. Load the page, make sure it's nothing but bright green, then edit the source, changing "green.gif" to "clear.gif" - voila!
This is good because it requires no javascript trickery which is easily disabled. When the user right-clicks and saves the image, he gets a 1x1 transparent gif. The downside, as mentioned, is that if the user really wants it, he can pull it from his cache or view the source. Viewing the source can be discouraged using document.write(unescape("%3c%69%6d%67%20%73%72%63%3d%22%72%65%61%6c%69%6d%61%67%65%2e%70%6e%67%22%3e")); but that's not exactly foolproof, either. If the user wants the image, there's always a way.
coldfire421
04-20-2011, 01:17 PM
yea and he can even press the print screen on his keyboard and then - voila! steal your photos LOL
webdeveloper.com
Copyright Internet.com Inc., All Rights Reserved.
Copyright Internet.com Inc., All Rights Reserved.