Forum Moderators: open
Search:
site:webmasterworld.com protect images
site:webmasterworld.com stop image thrft
or similar search strings. There are dozens of threads. All with the same answer. The only thing that will stop an amateur is Flash, but Flash-crackers are readily available.
If you can live with it, you can use visible watermarks with low opacity. There are embedded data and image search options to find theft. Strong copyright protection text pages that might make some people think before taking yours instead of someone elses.....
You cannot stop anyone from taking your images. Period. End of story.
We really need a permalink on 'image/code protection' that can be used to direct this and similar questions. There may be one in the 'library', and while it's got some great stuff in it I've never found it very usable; just interesting to look through randomly. Ought to see if I could put together a group and develop a comprehensive consensus answer for this. This only thing that comes up more often are links snipped for TOS. These threads need to die on post #2.
I answered the question and did provide two good search options which will provide plenty of reading to start with. Also made a couple of alternate option suggestions on making their particular images less attractive targets than those of someone else.
Just let them die for lack of response if one gets tired of seeing them.
I don't think that this is a good solution. To be able to reach for thorough threads addressing the same-same-same questions would be a great 'value added' service to all. Letting the question die increases the churn of new users that go away also. These are the links that would make a great library. Or the wheel can be reinvented weekly. Questions that arise regularly on any of our sites are nuked with better pages or resource links. We do not answer the phone or trade emails on the same question forever. Who can afford to do that and leave as a perpetual issue?
I don't get the library, as implemented. It is 6,600 threads thrown in a hopper; that they are good becomes irrelevant. site: gives one a better chance of turning over the right rock.
Not my place to make issue I don't reckon. No shortage of Moderators. If they're okay, then - well, it's not like I've got a horse in the race, or a stake in options.
On average, thread lifespan, even for a good question drilled down to a great answer, is but a few days at the most; I know this.
[OT apology]
It is 6,600 threads thrown in a hopper...site: gives one a better chance of turning over the right rock.
Gotta agree on this one, those threads would have so much more value by improving the way they are accessed.
[/OT apology]
6,600 threads thrown in a hopper
If you click on the Library link within a given forum, you get filtered results just for that forum (that's 268 threads for the HTML Forum). However, usability is still pretty poor.
What you're seeing, with just a few exceptions, is threads that were featured on the Home Page at some time. That means some of the FAQs are not going to be in there.
I, too, have made use of the "library" and find it lacking in organization and ease of use, though I USUALLY find answers there... however, the search option at WW does a better job if you know how to phrase the query to get results. Apologies to all if I appeared callous and uncaring!
How can i disable dragging images in HTML?
The OP does explicitly state "dragging" of images, not necessarily the "copying" of images. (rocknbil does touch on this)
Although in most (all?) browsers you can drag images off the page into other applications (drag and drop), some of the latest browsers (FF3, Opera, but not IE8 or Google Chrome) give you a ghosted preview of that image as you drag it - this could be perceived as 'dragging images'.
Although, AFAIK, you can't disable the drag and drop operation per se (without messing with JavaScript / disabling mouse clicks etc.) and AFAIK you can't disable this ghosted preview whilst dragging in your HTML that will effect your users (as with something like IE's 'imagetoolbar' META tag), but you can disable this ghosted preview in the browser - in FF3 at least:
Google: "Tweak: Disable Drag & Drop (Preview) Images"
1. In a new tab type about:config
2. In the filter field type nglayout.enable_drag_images
3. Double-click on the entry below so the value is false
4. Close the tab (no restart needed)
(Not sure about Opera)
1) I dropped the hammer pretty hard. (Something that I usually avoid due to the risk level of crossing the arrogance line, then needing a rock to crawl under if getting it wrong. Not the reputation that I would want coming to people's minds when they see D_Blackwell.)
2) I didn't even welcome poor krugi, making his very first post.
3) You defended the OP from a hard line response - not unreasonable (though I would have done it anyway in this case).
4) I did make the leap from what the OP asked to the purpose that I presumed was intended. Normally, I would use much more caution about that, or offer qualifiers along the way, but it seemed very unlikely to be necessary for this quesion.
5)
Ought to see if I could put together a group and develop a comprehensive consensus answer for this. This only thing that comes up more often are links snipped for TOS. These threads need to die on post #2.
I was actually serious about this and what brought the library to mind. Of course, many questions or variants of same come round and round - that will always be the case, but there are a few constant topics that could be quickly pointed to a highly thorough reference that covers the options; the pros and cons... I have various libraries; email responses for example, that I can copy, tweak for specifics, and fire off. Very hand weapon.
People won't look for it, or read it even if they know it's there - but once dragged to the thread, that ought to do the trick for most people. There may be follow-up questions that result in an edit to the 'master answer'.
6) encyclo has very nice "Guide to Posting HTML and CSS" that is pinned - but I suspect that it sees minimal use, which is a shame. If they only followed item #1, #2, and #4 a lot of problems would be solved before posting. In the CSS forum, a lot of questions answer themselves if one just strips it down to the problem.
<rant> What really irritates me is the code posted always has to be jiggered around before I can even look at the problem. Grrr. It should really be, if only as courtesy, dropped in 'test ready'. Often, more time is spent reorganizing the 'example dump' than fixing the problem. LOL </rant>
ondragstart="return false" onselectstart="return false"
Thanks for everybody who tried to help.
Now, i have another thing.
I want to disable copying images.
How? (:
Here's the bottom line. For anyone to display content, a copy of that content MUST already be downloaded to their computer. You can make it more difficult for them to access their local copy, but you cannot stop them.
I have clients who start out demanding this kind of protection - and I've demonstrated over and over that it does not exist. The folks who would do the most damage to your intellectual property will be ones who are most educated in capturing your images and content. Any obstacles you try to put in place will only disturb your most "ordinary" visitors - the ones you need to keep happy!
For example, disabling right click with javascript is a common approach. But there are many other options available through right click that enhance browsing and make it easier. If you deny all of them to a javascript-enabled visitor, then you drive many visitors away.
Here's my advice: give up your quest, it is futile.
[edited by: tedster at 5:25 pm (utc) on Sep. 9, 2009]