Welcome to WebmasterWorld Guest from 184.108.40.206
Forum Moderators: open
By Deactivate I mean either they try to view the source and it gives back an error message - or they hit view source and nothing - litterly - nothing is showing...
My instructor at the collage has us uploading our assignments to the servers and I don't want someone taking the easy way out by viewing my pages and copying the source.
I do mean more then just right clicking by the way, and if theres an aproach to get around the more-so tricky loopholes I'm all ears (nobody is that smart but, knowledge is power ;) )
[Our local uni sets each student up for protected space once they're registered; all uploads for all classes go into that space, and the profs have some sort of admin access for their own classes/students....]
I know frames are not an ideal solution, but if you use them, all the visitor gets is the frameset code on the view source option - since the frame pages appear as SRC links instead of actual pages. In other words, the visitors cannot see your code...
Err...with lots of browsers you can just right-click in the frame whose source you want to see...
there MUST be a way though...
2. Eeplace all text with its named entity or numeric equivalent. Again, browers will ignore, but a source-reading human will have a headache:
3. Replace every space in the text with multiple spaces and/or newlines and/or tabs (up to several hundred in each case). Browsers will collapse the whitespace back, But a text editor won't:
--can't show an example -- WMW would collapse it.
4. Randomly interspere the text with long HTML comments:
<p><!--Hello this is the bit to read--><tabel>h<h19>i</hmtl> </divide>t<!--read this--><fone>h</pp>e<heading>r<!--notes on class assignment--><weak>e<ahref></p>
5. Also add trash attributes to all real and imaginary tags:
<p colour=off-white><!--Hello this is the bit to read--><tabel claus="heading">h<h19 backgrind=transparent>i</hmtl> </divide>t<!--read this--><fone ringtone="annoying">h</pp>e<heading styles="">r<!--notes on class assignment--><weak caller-id="off">e<ahref></p>
6. Ask yourself: is it is really worth it? Anyone with a tint bit of programming knowledge, or a HTML cleaner can reverse this in a moment. And remember: if valid HTML is needed for a course credit, you've just failed.
People can link to your images by using your URL and filename in their image tag, src="yourdomain.com/yourimage.jpg". When someone views their page it pulls the image from your server. It's called "hotlinking". You can block hotlinking in Apache, I don't know about IIS servers.
That is very easy to fix. Either:
- sniff the URL of the referring page, and do not show the image if the referrer is not your own site, or
- look at your log files, and ban access from other sites that are linking to your images (add the IPs to your .htaccess file).
Thats the good part ..
The "bad part"? ..
If the visitor isn't using IE they cant see squat ..
Most visitors back out before they see anything even if they are using IE ( cos you need to preload all your images ..load time is very long ..See "Brett's first rule" about why that is a bad thing...knows a thing or two that Mr Tabke ;).
You've got to hide your image folders and do htaccess stuff anyway to prevent hotlinking..
BUT ..to hide your image folders from the bots ..you got to declare them in "robots.txt"...
and anyone who really knows what they are doing can go into their temporary internet files and copy out the image while they are "live "into your site and use them later ( even if you had the file type renamed while they were "visiting" ...This is how one would "save" "streamed" Flash etc )...
took ronin under 2 minutes to work out how to get around my stuff ( I also had forgotten to do htaccess..but anyway )...
and the only way to block screen capture successfully ..
..actually kills all the visitors "clipboard" and right click facility for the remainder of their session ..requiring them to reboot to get it back ..This does not make you "flavour of the month" ...
And I think the latest IE blocked the "hole" I used ..course they left lots too ..but honestly there are more interesting things to do than to hack visitors boxes via IE ...
All of which is a RPITA ...and you actually get more ROI without all this ...
You really want to do it?
( self edited .."speeling" )
taking what doesn't belong to them. And it's only just a few, 99.9% of my visitors are the best and very appreciative of the service I offer. So, I've disabled the right click,
There's some strangely one-sided logic here.
You are taking something that doesn't belong to you: namely my right click.
That's a form of denial of service attack on my hardware.
You should aspire to be a be welcome guest in my browser window, not a vandal.
I have many other uses for a right click.
Should I ever visit your website, I'd expect to see a large warning notice on the landing page for what you intend to do, so I can agree and continue, or exit to find a more welcoming site to browse.
Unfortunately, it's been made perfectly clear to some of us over time that BECAUSE of the "free and open" situation as regards the internet, some of our vaunted privacies are simply not viable options any more. No matter what one's art, whether graphics, music, video, fiction, technical writing, news stories - or just plain the "art" of html and CSS - there is truly only one way to keep it from being at some point used in a way one doesn't want (ripped off in toto, improperly credited or not credited at all, used on sites which promote all the things you've specifically disallowed etc. etc. ad infinitum ad nauseam), and that singular way of keeping it safe is to simply NOT put it on the web.
For many of us, for many reasons, that's not an acceptable choice. So we do our level best to limit the potential misuses by accessing Copyscape; by copyrighting (and registering the copyrights); by watermarking; by keeping multitudes of backups, revision after revision, with dates all over them. None of this is perfect. All of it will help, but one still finds one's work in places one never gave permission for use. At that point one sends out emails, uses DMCA, hires an attorney - whatever it takes....
While the "ripping off" is probably inescapable, is the alternative better if that alternative is to NOT have the free and open web?
Ultimately, it is your website so you do what you like with it (though subject to accessibility and other laws in your locality).
But a site that can be "stolen" by copying the surface appearance is not making full use of what makes the web a success:
You get the idea. Your CGI scripts give you depth that cannot easily be copied. A site without such depth is very shallow, and easy to replicate.
So look in that direction for a solidity and uncopyable uniqueness to your web efforts. That way lies real success.