Comments on: Content-Stealing Jerks http://www.kevinwilliampang.com/2009/03/28/content-stealing-jerks/ ASP.NET Developer. ALT.NET Supporter. Pragmatic Programmer. Published Writer. Thu, 02 Sep 2010 01:11:40 +0000 hourly 1 By: tnomeralc web design toys http://www.kevinwilliampang.com/2009/03/28/content-stealing-jerks/#comment-785 tnomeralc web design toys Sat, 25 Apr 2009 04:05:41 +0000 /post/Content-Stealing-Jerks.aspx#comment-785 this is a problem now a days, a lot of auto blog and duplication machine are being made and sell on different webmaster community. Only you can do is contact the blog owner or the hosting provider. this is a problem now a days, a lot of auto blog and duplication machine are being made and sell on different webmaster community. Only you can do is contact the blog owner or the hosting provider.

]]> By: CSJ http://www.kevinwilliampang.com/2009/03/28/content-stealing-jerks/#comment-783 CSJ Mon, 20 Apr 2009 05:49:17 +0000 /post/Content-Stealing-Jerks.aspx#comment-783 Wow, great post. Can I copy and paste this verbatim onto my site? hehe, just kidding. Wow, great post. Can I copy and paste this verbatim onto my site?

hehe, just kidding.

]]> By: Hazel http://www.kevinwilliampang.com/2009/03/28/content-stealing-jerks/#comment-782 Hazel Fri, 17 Apr 2009 14:58:43 +0000 /post/Content-Stealing-Jerks.aspx#comment-782 Wow, this surely sucks!! No originality at all, but thanks for sharing this experience with us, now I know what to do in case that happens to me ;) Wow, this surely sucks!! No originality at all, but thanks for sharing this experience with us, now I know what to do in case that happens to me ;)

]]> By: Max Pool http://www.kevinwilliampang.com/2009/03/28/content-stealing-jerks/#comment-781 Max Pool Fri, 17 Apr 2009 11:01:10 +0000 /post/Content-Stealing-Jerks.aspx#comment-781 Don't worry about the scraping too much. Google will catch up with them and pop them out of any organic search results... Don’t worry about the scraping too much. Google will catch up with them and pop them out of any organic search results…

]]> By: dagobart http://www.kevinwilliampang.com/2009/03/28/content-stealing-jerks/#comment-777 dagobart Wed, 08 Apr 2009 02:49:04 +0000 /post/Content-Stealing-Jerks.aspx#comment-777 Ha, strike! Someone copied another piece of my work, though kept the plaintext shortlink to the original post in it: Here's the rip-off: http://kitchen.linkablez.info/2009/04/07/for-purpose-of-reference-anti-alias-emacs/. (Shortlink to OP is is.gd/riyx). I actually didn't expect the post to get spread but prepended it with the shortlink nevertheless. So, this worked out. :) Turned out it got a rank on reddit. Now I wonder whether everything ranked on sites like reddit might get spread. Ha, strike! Someone copied another piece of my work, though kept the plaintext shortlink to the original post in it: Here’s the rip-off: http://kitchen.linkablez.info/2009/04/07/for-purpose-of-reference-anti-alias-emacs/. (Shortlink to OP is is.gd/riyx).

I actually didn’t expect the post to get spread but prepended it with the shortlink nevertheless. So, this worked out. :) Turned out it got a rank on reddit. Now I wonder whether everything ranked on sites like reddit might get spread.

]]> By: Dawn http://www.kevinwilliampang.com/2009/03/28/content-stealing-jerks/#comment-776 Dawn Sun, 05 Apr 2009 02:10:08 +0000 /post/Content-Stealing-Jerks.aspx#comment-776 Not sure if you've seen the site lately but I looked today and the article has been "slightly" modified it is now the "Top 16 Things That absolutely Annoy Programmers." While some original items were included this does not change the fact that the majority of the content is pure copyright infringement. Not sure if you’ve seen the site lately but I looked today and the article has been "slightly" modified it is now the "Top 16 Things That absolutely Annoy Programmers." While some original items were included this does not change the fact that the majority of the content is pure copyright infringement.

]]> By: Snats http://www.kevinwilliampang.com/2009/03/28/content-stealing-jerks/#comment-775 Snats Thu, 02 Apr 2009 18:55:33 +0000 /post/Content-Stealing-Jerks.aspx#comment-775 The saga continues, and Delimit continue apace with copying and pasting any and all sundry and claiming it as their own. Onward with the take down notices and notifying the advertisers on the theft site about it. http://www.reddit.com/r/Design/comments/89dvr/indications_that_you_are_charging_way_too_little/ The saga continues, and Delimit continue apace with copying and pasting any and all sundry and claiming it as their own. Onward with the take down notices and notifying the advertisers on the theft site about it.

http://www.reddit.com/r/Design/comments/89dvr/indications_that_you_are_charging_way_too_little/

]]> By: dagobart http://www.kevinwilliampang.com/2009/03/28/content-stealing-jerks/#comment-774 dagobart Thu, 02 Apr 2009 17:34:22 +0000 /post/Content-Stealing-Jerks.aspx#comment-774 @ZagNut, @Kevin. Yepp. And once you publish your content as text, the opposition could take it, make an image out of it and watermark it with their signature. (That was the issue I originally wanted to point out.) On the other hand, publishing content as pics only would a) make it unsearchable/unfindable nd b) likely scare 'legitimate' RSS readers away, because of (relatively) big downloads that might be handled badly by whatever RSS readers they use and still would be un-indexable, therefore not worth to be archived at all. -- In effect, in my humble opinion, such a step would effect in pushing you off the web, self-made. Also, watermarks are nothing magic. You can detect them. And, once done so, you can remove them (if I remember correctly). So, you might be best off if you'd do the watermarking without mentioning at all.   I see 2.5 possible ways to fight unwanted rip-offs: a) Watermark _the text_, like with 'nbsp's instead of usual whitespaces or 'ndash'/'mdash'es instead of minusses etc. b1) register your content with a centralized service b2) A network of friend blogs might be able to become such a 'witnesses' network also. And blogging is about conversation and bonding anyway, so this wouldn't hurt anyways. @ZagNut, @Kevin. Yepp. And once you publish your content as text, the opposition could take it, make an image out of it and watermark it with their signature. (That was the issue I originally wanted to point out.)

On the other hand, publishing content as pics only would a) make it unsearchable/unfindable nd b) likely scare ‘legitimate’ RSS readers away, because of (relatively) big downloads that might be handled badly by whatever RSS readers they use and still would be un-indexable, therefore not worth to be archived at all. — In effect, in my humble opinion, such a step would effect in pushing you off the web, self-made.

Also, watermarks are nothing magic. You can detect them. And, once done so, you can remove them (if I remember correctly). So, you might be best off if you’d do the watermarking without mentioning at all.
 

I see 2.5 possible ways to fight unwanted rip-offs:
a) Watermark _the text_, like with ‘nbsp’s instead of usual whitespaces or ‘ndash’/'mdash’es instead of minusses etc.
b1) register your content with a centralized service
b2) A network of friend blogs might be able to become such a ‘witnesses’ network also. And blogging is about conversation and bonding anyway, so this wouldn’t hurt anyways.

]]> By: ZagNut http://www.kevinwilliampang.com/2009/03/28/content-stealing-jerks/#comment-773 ZagNut Thu, 02 Apr 2009 15:48:36 +0000 /post/Content-Stealing-Jerks.aspx#comment-773 @Kevin touche... I guess there's no alternative than to simply destroy them... @Kevin

touche…

I guess there’s no alternative than to simply destroy them…

]]> By: Kevin Pang http://www.kevinwilliampang.com/2009/03/28/content-stealing-jerks/#comment-772 Kevin Pang Thu, 02 Apr 2009 10:41:45 +0000 /post/Content-Stealing-Jerks.aspx#comment-772 @ZagNut It would work, although I'm wondering if that would be throwing out the baby with the bathwater. There are some adverse effects of doing this including: 1. [b]Search engine optimization[/b]. If all the Google spider sees is a big image, they're not going to be able to index on any keywords in the post. 2. [b]Copy/paste.[/b] I post code snippits here and there in my posts and having them be embedded in an image would prevent people from copy/pasting them easily. 3. [b]Searchability.[/b] This is similar to #1, but when people do a ctrl-f search within a post, it wouldn't work. 4. [b]Annoying for me to maintain.[/b] I make revisions to my posts all the time as new information rolls in. Having to update the image would be a pain in the butt. @ZagNut

It would work, although I’m wondering if that would be throwing out the baby with the bathwater. There are some adverse effects of doing this including:

1. [b]Search engine optimization[/b]. If all the Google spider sees is a big image, they’re not going to be able to index on any keywords in the post.
2. [b]Copy/paste.[/b] I post code snippits here and there in my posts and having them be embedded in an image would prevent people from copy/pasting them easily.
3. [b]Searchability.[/b] This is similar to #1, but when people do a ctrl-f search within a post, it wouldn’t work.
4. [b]Annoying for me to maintain.[/b] I make revisions to my posts all the time as new information rolls in. Having to update the image would be a pain in the butt.

]]>