NOSAVE inside img tag?

[Cas]

A long time ago, I used Netscape Composer to create my very simple web pages, and I remember an attribute of the img tag that was NOSAVE, and I thought it meant that the image wouldn't be downloaded to a viewer's computer, but stay on the server (??). I've been able to protect some images on my site by disabling the IE image tool bar, the right-click and the cut&paste, drag etc.; by forcing the print command to print another (dummy) page (in IE); and by using the nifty tranparency idea put forth on another thread here. A nice side-effect of the transparency is that in Firefox's print preview it stops someone from lifting the image there (which was a loophole of the disabling right click etc.). But, the jpg still shows up in the temporary internet files folder for IE users. I'm not sure, yet, where those files are in Firefox (which I use).

So -- wouldn't something like the old NOSAVE work? Is there something like that still in existence? I suspect that was an old html thing that only applied to Netscape users, but that's merely a guess.

thanks in advance!

[jscheuer1]

How many pictures have you protected this way. Who was trying to steal them?

[Twey]

I thought it meant that the image wouldn't be downloaded to a viewer's computer, but stay on the server
And how did you think the user viewed an image to which s/he didn't have access? :) I've never used this attribute, but I would guess it prevents right-click saving: a perfunctory measure at best.

It is not possible to totally hide an image. User see, user grab. The only way an image can be viewed is if it's been downloaded to the user's computer already, in which case they have full access to it if they know where to find it. The only thing you can do is watermark your images.

[Raghavendra]

Yes you can always water mark the Images.
Also I think you can write a Java Applet that only shows the image and disables image selection and copy features.

Raghavendra.V

[Twey]

That's one idea, but applets are slow to load and the user could still get the image from inside the JAR. The only way of doing this would be to have the applet generate the image.

[Cas]

How many pictures have you protected this way. Who was trying to steal them?

I protected photos that were posted to one page, so the entire page has all of the protections I listed. Code for which I found here. I know about watermarking, and have that capacity (an account with some company affiliated with my Adobe photoshop) but that wouldn't be applicable for the photos I posted. I think that people coming to my site aren't going to be that sophisticated to be able to find their internet cache (if they even know they have a cache file, lol), now that I think about it.

But there is an old laptop sitting around here that has that old Netscape Composer on it, and I'm going to check out what NOSAVE's description was.

[Twey]

It was a checkbox marked "leave image at its original location." Only applicable, I believe, for local images.

[Cas]

It was a checkbox marked "leave image at its original location." Only applicable, I believe, for local images.

After talking to someone else who used to use Composer, as well, I think I understand to what you're referring by "local images," and I get what she's saying, that it was a way for Composer to create the path for the image and not make a copy for a (possibly) different directory than where you wanted the image stored. At least, that was always her understanding of what that meant.

But the reason I was always confused by the command was because "NOSAVE" would then be put into the img tag, in the file, for any browser to read. If it was only an internal checkbox for Composer, to be followed during the time you were creating your pages and building your site, why put that in the html code? I assume then that the Netscape browser did nothing with that command? Ignored it? Otherwise anyone with Netscape looking at your site would have a computer trying to do something....

I realize this is fairly OT and all, considering the intial question I had. But I'm curious, nonetheless.

[Twey]

No, it's applicable to anyone viewing the page who has already downloaded the image. Although only using Netscape 4, of course. This effectively means anyone using the author's computer to view the page, being as most people won't copy the images to other directories or modify a page before viewing. It may also be used for saving pages to disk. This is no longer used as most browsers nowadays handle local images differently automatically.