Re: Image Pirating [protecting against]
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 50953
interpreted = N
texte = The only thing you can do is to post notices, watermarks and follow the copyright law guidelines found at http://www.loc.gov/copyright/ and know how/if your protected.The no-right clicking javascript thing is something you find on a warez or porn site (not that I've ever been to either :)Other tricks will only fool those with no experience on surfing the internet for a very short time.Besides, if someone wants your images, all they have to do is to open up their browsers cache.GK-----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of Donovan home EHG Sent: Friday, June 06, 2003 10:08 AM To: WebDNA Talk Subject: Image Pirating [protecting against] Hello, I have a job coming up where I will need to make an effort to protect images. Here are the things I know of:1.) watermarked images 2.) copywrite text 3.) 72 PPI images (obvious) 4.) disabling the right click (controversial) 5.) In the source put a comment about copywriting. 6.) copywrite your images.I have also heard about placing a transparent gif on layer over the image... doesn't prevent someone from looking at the source, but it does help with hinderance.Another thought is that some browsers (IE 5 for exampe [I believe]) adhere to w3c suggestions that when a page is arrived at via method=post from a form AND when the http mime headers have an expired expires value, the source is not available to the user.Beyond this, I don't know of any other way to protect the images becauseit seems its always availabe either via screen shot or the source.What are your thoughts?Thanks, Donovan------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
The only thing you can do is to post notices, watermarks and follow the copyright law guidelines found at http://www.loc.gov/copyright/ and know how/if your protected.The no-right clicking javascript thing is something you find on a warez or porn site (not that I've ever been to either :)Other tricks will only fool those with no experience on surfing the internet for a very short time.Besides, if someone wants your images, all they have to do is to open up their browsers cache.GK-----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of Donovan home EHG Sent: Friday, June 06, 2003 10:08 AM To: WebDNA Talk Subject: Image Pirating [protecting against] Hello, I have a job coming up where I will need to make an effort to protect images. Here are the things I know of:1.) watermarked images 2.) copywrite text 3.) 72 PPI images (obvious) 4.) disabling the right click (controversial) 5.) In the source put a comment about copywriting. 6.) copywrite your images.I have also heard about placing a transparent gif on layer over the image... doesn't prevent someone from looking at the source, but it does help with hinderance.Another thought is that some browsers (IE 5 for exampe [I believe]) adhere to w3c suggestions that when a page is arrived at via method=post from a form AND when the http mime headers have an expired expires value, the source is not available to the user.Beyond this, I don't know of any other way to protect the images becauseit seems its always availabe either via screen shot or the source.What are your thoughts?Thanks, Donovan------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Gary Krockover
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Nested vs conditional (1997)
[shownext] and descending order (1997)
Separate SSL Server (1997)
Searching with a form (2000)
authenticate and password (1998)
PCS Frames (1997)
[WebDNA] parsing xml (2010)
Authenticate (1997)
Don't know if this is a sily question... (2003)
Generating Report Totals (1997)
NTbeta18 corrupted? (1997)
[encrypt] blues.... (2000)
syntax question, not in online refernce (1997)
Multiple prices (1997)
WCS Newbie question (1997)
bcc and sendmail (2001)
[Include] within a .dna file *further weirdness* (2005)
Opinion: [input] should be called [output] ... (1997)
Which [index]? (1997)
[WebDNA] Advices for Linux Config (2017)