Fwd: Image Pirating [protecting against]
2003
It keeps the original formatting.
interpreted = N
texte = This discussion just occurred on the MGI list as well. A strategy that someone suggested there is to rename their enclosing folder once an hour (or whatever interval you choose).In WebDNA I expect you would set a trigger or use a cron script to generate a path like
. In MGI this idea relies on storing the true path in a variable with a scope of the whole site, but in WebDNA I expect that this could be handled by a simple db file. Just reference the variable with the correct path so the pages in your site automatically recognize the new link. This won't foil everybody, but it should cut down on bot-based image hijacking considerably.For the images that were linked from outside the site, some suggested trapping for the referrer to limit local access via a rule in a server plugin called Welcome (http://welcome.pardeike.net/pages/rulesexamples.html#a). Welcome is specific to WebStar and QuidProQuo on Mac Classic, but maybe the same functionality can be reproduced in WebDNA within ShowIF contexts. Others had some fun changing the content of the image to embarrass the thief (this, while highly amusing, is probably not very scalable).Dave Hurley Biology Department University of Washington On Friday, June 6, 2003, at 08:07 AM, Donovan home EHG wrote:>> 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
|
. In MGI this idea relies on storing the true path in a variable with a scope of the whole site, but in WebDNA I expect that this could be handled by a simple db file. Just reference the variable with the correct path so the pages in your site automatically recognize the new link. This won't foil everybody, but it should cut down on bot-based image hijacking considerably.For the images that were linked from outside the site, some suggested trapping for the referrer to limit local access via a rule in a server plugin called Welcome (http://welcome.pardeike.net/pages/rulesexamples.html#a). Welcome is specific to WebStar and QuidProQuo on Mac Classic, but maybe the same functionality can be reproduced in WebDNA within ShowIF contexts. Others had some fun changing the content of the image to embarrass the thief (this, while highly amusing, is probably not very scalable).Dave Hurley Biology Department University of Washington On Friday, June 6, 2003, at 08:07 AM, Donovan home EHG wrote:>> 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 DOWNLOAD WEBDNA NOW!
Top Articles:
Talk ListThe 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...