Comments on: Using CSS to Thwart Content Theft

By: Trevor

Trevor — Tue, 31 Mar 2009 16:23:49 +0000

There are other issues as well. Some content gets copied for innocent reasons like emailing to a friend or for research. Tynt’s Tracer reveals what content is being copied from your website and automatically adds an attribution link back to your original content if it is lifted from your site and pasted into an email, blog or website. This way you get the traffic and the credit.

Visit www.tynt.com <http://www.tynt.com> to sign up now.

Trevor
Do you know what is being copied from your site?

By: Jonathan Bailey

Jonathan Bailey — Wed, 14 Jan 2009 01:16:12 +0000

Sorry to hear that it didn’t work fo ryou but I’m not wholly surprised, I knew it was a very limited approach to the issue. If you need any help, send me an email and I’ll see what I can suggest.

By: Eszter

Eszter — Tue, 13 Jan 2009 02:43:01 +0000

Well, it definitely doesn’t work for me, tried it with four different posts.

By: How to use CSS to prevent content theft « WP vs TP

How to use CSS to prevent content theft « WP vs TP — Tue, 19 Aug 2008 22:06:12 +0000

[...] The idea for this comes from Plagiarism Today. [...]

By: How to use CSS to prevent content theft « TypePad versus WordPress

How to use CSS to prevent content theft « TypePad versus WordPress — Tue, 19 Aug 2008 22:04:37 +0000

[...] The idea for this comes from Plagiarism Today. [...]

By: Three artices of interest « Mindtracks

Three artices of interest « Mindtracks — Tue, 19 Aug 2008 21:46:15 +0000

[...] August 20, 2008 Three artices of interest Posted by sharonb under Tips, Typography, Webdesign | Tags: copyright, CSS, hosting, plagerism, Typography | Plagiarism Today has published an interesting CCS technique to counter or at least frustrate anyone who is scraping your site. Check out the article Using CSS to Thwart Content Theft. [...]

By: Jonathan Bailey

Jonathan Bailey — Tue, 19 Aug 2008 17:49:32 +0000

I am sorry to hear about your problems in this area, if I can help in any way, please let me know.

You’re very welcome for the help and please let me know if there is more that I can do!

By: Susan

Susan — Tue, 19 Aug 2008 17:36:51 +0000

Dear Jonathan, I hesitated to put my website back-up because people were stealing the content from my uncle’s book (used with permission) The copyright of the book was updated again during the 1990s. It would be wonderful to so many people to have the information concerning genealogy, with fun journal stories and pioneer courage. I hope I can keep studying this page and figure this out. Unfortunately, when I was uploading my pages, I avoided Java and css, thinking it was just too much to learn. Now, I need to learn better the pages in the correct resolution and need to learn Java and css, anyway. Thank you so much for your help! It will keep my family’s hard work safe and not used to make someone else money, by selling it as their own. I was just sharing out of love of my family and gave complete credit to those that worked so hard for our family to have. (((hugs))) Susan Lazenby Santa Paula, California

By: Jonathan Bailey

Jonathan Bailey — Fri, 08 Aug 2008 04:16:01 +0000

Mike,

I agree that the CSS solution has serious flaws but, then again, so does any DRM technique. The solution you present, for example, won’t wok on those who turn of referrals (which includes many of my privacy-buff friends) and will not work in all environments as many bloggers don’t have access to their server config files.

That being said, I generally think technology solutions are a waste for many of the reasons you list, still, I discuss them for those who are interested. If you think that a technology-based approach is best, you need to decide what works for you in your situation with your needs.

You definitely present a good idea for some and I agree it is superior in many ways, but I think every method will have its limitations.

That’s fair to say…

By: Jonathan Bailey

Jonathan Bailey — Fri, 08 Aug 2008 04:16:01 +0000

Mike,

I agree that the CSS solution has serious flaws but, then again, so does any DRM technique. The solution you present, for example, won't wok on those who turn of referrals (which includes many of my privacy-buff friends) and will not work in all environments as many bloggers don't have access to their server config files.

That being said, I generally think technology solutions are a waste for many of the reasons you list, still, I discuss them for those who are interested. If you think that a technology-based approach is best, you need to decide what works for you in your situation with your needs.

You definitely present a good idea for some and I agree it is superior in many ways, but I think every method will have its limitations.

That's fair to say...