Re: Image Pirating [protecting against]

This WebDNA talk-list message is from

2003


It keeps the original formatting.
numero = 50955
interpreted = N
texte = Well, the point is prudent measures. I suppose from your comments below a HTTP-EQUIV=pragma CONTENT=no-cache wouldn't hurt, though browsers might ingore it.What I have now is: 1.) (digitally) watermarked images (possibly using a service such as (www.digimarc.com) 2.) copywrite text (possibly within graphic) 3.) disabling the right click (controversial) 4.) In the source put a comment about copywriting. 5.) copywrite your images. 6.) use a table with a background image as the regular image and with a transparent gif the same size as the table and within the table (over the bgimage). 7.) HTTP-EQUIV=pragma CONTENT=no-cache 8.) Arriving at the page via method post and setting the http expires header to history. DonovanGary Krockover wrote:> 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 because > > it 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/ ------------------------------------------------------------- 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:

    
  1. Re: Image Pirating [protecting against] (Daniel Schutzsmith 2003)
  2. Re: Fwd: Image Pirating [protecting against] (Donovan home EHG 2003)
  3. Re: Fwd: Image Pirating [protecting against] (Gary Krockover 2003)
  4. Re: Fwd: Image Pirating [protecting against] (Donovan home EHG 2003)
  5. Re: Fwd: Image Pirating [protecting against] (Donovan home EHG 2003)
  6. Re: Image Pirating [protecting against] (John Hill 2003)
  7. Fwd: Image Pirating [protecting against] (Dave Hurley 2003)
  8. Re: Image Pirating [protecting against] (Donovan home EHG 2003)
  9. Re: Image Pirating [protecting against] (Donovan home EHG 2003)
  10. Re: Image Pirating [protecting against] (Gary Krockover 2003)
  11. Re: Image Pirating [protecting against] (John Hill 2003)
  12. Image Pirating [protecting against] (Donovan home EHG 2003)
Well, the point is prudent measures. I suppose from your comments below a HTTP-EQUIV=pragma CONTENT=no-cache wouldn't hurt, though browsers might ingore it.What I have now is: 1.) (digitally) watermarked images (possibly using a service such as (www.digimarc.com) 2.) copywrite text (possibly within graphic) 3.) disabling the right click (controversial) 4.) In the source put a comment about copywriting. 5.) copywrite your images. 6.) use a table with a background image as the regular image and with a transparent gif the same size as the table and within the table (over the bgimage). 7.) HTTP-EQUIV=pragma CONTENT=no-cache 8.) Arriving at the page via method post and setting the http expires header to history. DonovanGary Krockover wrote:> 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 because > > it 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/ ------------------------------------------------------------- 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/ Donovan home EHG

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:

Keep away (1997) Re:FYI: Error message (1996) email preferences on NT (1997) WebDNA Developer Resource Center (2002) Bug Report, maybe (1997) Re:quit command on NT (1997) PCS Emailer's role ? (1997) Adding new customer numbers sequentially (1997) More on the email templates (1997) Emailer (WebCat2) (1997) WebCat editing, SiteGuard & SiteEdit (1997) Size limit for tmpl editor ? (1997) Only charge card when product shipped ? (1997) Help! (2000) form data submission gets truncated (1997) Can this be done? (2003) quotes and truncating? (1997) WebDNA & HTML Problems (2003) Weird happenings (1998) Help formatting search results w/ table (1997)