4 replaced http://stackoverflow.com/ with https://stackoverflow.com/
source | link

If you are looking for things that make the image slightly harder to copy and arn't worried about handling things like screenshots, which are by definition lossy, then you may be interested to to try BASE64 encoding the images and putting them into the page's source.

See here: http://stackoverflow.com/questions/1207190/embedding-base64-imageshttps://stackoverflow.com/questions/1207190/embedding-base64-images

This seem fairly straight forward and allows you to not have a separate URL for the image. Pairing this with overlaying a transparent div, may be a relatively effective solution against non-developers.

Once again, this offers zero defence against screenshots, but I don't think you will find a good solution that is technical in nature.

If you are looking for things that make the image slightly harder to copy and arn't worried about handling things like screenshots, which are by definition lossy, then you may be interested to to try BASE64 encoding the images and putting them into the page's source.

See here: http://stackoverflow.com/questions/1207190/embedding-base64-images

This seem fairly straight forward and allows you to not have a separate URL for the image. Pairing this with overlaying a transparent div, may be a relatively effective solution against non-developers.

Once again, this offers zero defence against screenshots, but I don't think you will find a good solution that is technical in nature.

If you are looking for things that make the image slightly harder to copy and arn't worried about handling things like screenshots, which are by definition lossy, then you may be interested to to try BASE64 encoding the images and putting them into the page's source.

See here: https://stackoverflow.com/questions/1207190/embedding-base64-images

This seem fairly straight forward and allows you to not have a separate URL for the image. Pairing this with overlaying a transparent div, may be a relatively effective solution against non-developers.

Once again, this offers zero defence against screenshots, but I don't think you will find a good solution that is technical in nature.

3 added 4 characters in body
source | link

If you are looking for things that make the image slightly harder to copy and arn't worried about handling things like screenshots, which are by definition lossy, then you may be interested to to try BASE64 encoding the images and putting them into the page's sourcetry BASE64 encoding the images and putting them into the page's source.

See here: http://stackoverflow.com/questions/1207190/embedding-base64-images

This seem fairly straight forward and allows you to not have a separate URL for the image. Pairing this with overlaying a transparent div, may be a relatively effective solution against non-developersmay be a relatively effective solution against non-developers.

Once again, this offers zero defence against screenshots, but I don't think you will find a good solution that is technical in nature.

If you are looking for things that make the image slightly harder to copy and arn't worried about handling things like screenshots, which are by definition lossy, then you may be interested to to try BASE64 encoding the images and putting them into the page's source.

See here: http://stackoverflow.com/questions/1207190/embedding-base64-images

This seem fairly straight forward and allows you to not have a separate URL for the image. Pairing this with overlaying a transparent div, may be a relatively effective solution against non-developers.

Once again, this offers zero defence against screenshots, but I don't think you will find a good solution that is technical in nature.

If you are looking for things that make the image slightly harder to copy and arn't worried about handling things like screenshots, which are by definition lossy, then you may be interested to to try BASE64 encoding the images and putting them into the page's source.

See here: http://stackoverflow.com/questions/1207190/embedding-base64-images

This seem fairly straight forward and allows you to not have a separate URL for the image. Pairing this with overlaying a transparent div, may be a relatively effective solution against non-developers.

Once again, this offers zero defence against screenshots, but I don't think you will find a good solution that is technical in nature.

2 added 7 characters in body
source | link

If you are looking for things that make the image slightly harder to copy and arn't worried about handling things like screenshots, which are by definition lossy,which are by definition lossy, then you may be interested to to try BASE64 encoding the images and putting them into the page's source.

See here: http://stackoverflow.com/questions/1207190/embedding-base64-images

This seem fairly straight forward and allows you to not have a separate URL for the image. Pairing this with overlaying a transparent div, may be a relatively effective solution against non-developers.

Once again, this offers zero defence against screenshots, but I don't think you will find a good solution that is technical in nature.

If you are looking for things that make the image slightly harder to copy and arn't worried about handling things like screenshots, which are by definition lossy, then you may be interested to to try BASE64 encoding the images and putting them into the page's source.

See here: http://stackoverflow.com/questions/1207190/embedding-base64-images

This seem fairly straight forward and allows you to not have a separate URL for the image. Pairing this with overlaying a transparent div, may be a relatively effective solution against non-developers.

Once again, this offers zero defence against screenshots, but I don't think you will find a good solution that is technical in nature.

If you are looking for things that make the image slightly harder to copy and arn't worried about handling things like screenshots, which are by definition lossy, then you may be interested to to try BASE64 encoding the images and putting them into the page's source.

See here: http://stackoverflow.com/questions/1207190/embedding-base64-images

This seem fairly straight forward and allows you to not have a separate URL for the image. Pairing this with overlaying a transparent div, may be a relatively effective solution against non-developers.

Once again, this offers zero defence against screenshots, but I don't think you will find a good solution that is technical in nature.

1
source | link