Why I share
I think openness in geoscience is very important, and I feel we all have a duty to be open with our work, data, ideas when possible and practical. I certainly do believe in sharing a good deal of the work I do in my spare time. So much so that when I started this blog there was no doubt in my mind I would include an agreement for people to use and modify freely what I published. Indeed, I venture to say I conceived the blog primarily as a vehicle for sharing.
Some of the reasons for sharing are also selfish (in its best sense): doing so gives me a sense of fulfillment, and pleasure, as Matt Hall writes in Five things I wish I’d known (one of the essays in 52 You Should Know About Geophysics), you can find incredible opportunities for growth in writing, talking, and teaching. There is also the professional advantage of maintaining visibility in the marketplace, or as Sven Treitel puts it, Publish or perish, industrial style (again in 52 You Should Know About Geophysics).
How I used to share
A (very) cold shower
Unfortunately, one day last year I ‘woke up’ to an umpleasant surprise: in two days an online magazine had reposted all my content – literally, A to Z! I found this out easily because I received pingback approval requests for each of them (thank you WP!). Quite shocked, I confess, the first thing I did was to check the site: indeed all my posts were there. The published included an attribution with my name at the top of each post but I was not convinced this would be fair use. Quite the contrary, to me this was a clear example of content scraping, and the reason why I say that is because they republished even my Welcome post and my On a short blogging sabbatical post – in the science category! – please see the two screen captures below (I removed their information) of the pingbacks:
If this was a legitimate endeavour, I reasoned, a magazine with thoughtful editing, I was sure those two posts would have not been republished. Also, I saw that posts from many other blogs were republished en masse daily.
Limitations of Creative Commons licenses
I asked for advice/help from my twitter followers, and on WordPress Forums, while at the same time started doing some research. That is when I learned this is very common, however being in good company (google returned about 9,310,000 results when searching ‘blog scraping’) did not feel like much consolation: I read that sites may get away with scraping content, or at least try. I will quote directly from the Plagiarism Today article Creative Commons: License to Splog?: “They can scrape an entire feed, offer token attribution to each full post lifted (often linking just to the original post) and rest comfortably knowing that they are within the bounds of the law. After all, they had permission …Though clearly there is a difference between taking and reposting a single work and reposting an entire site, the license offers a blanket protection that covers both behaviors”.
Fight or flight?
Yes, Creative Commons have mechanisms that allow fighting of this abuse, but their effectiveness is yet to be proved (read for example this other article by Plagiarism Today, Using Creative Commons to Stop Scraping). Notice these articles are a bit out of date but as far as I could see things have not improved much. The way is still the hard way of tracking down the culprit and fighting through legal action, although social media support helps.
It is possible to switch to a more restrictive Creative Commons license like the Attribution-NonCommercial-NoDerivs (perhaps modified as a CC+), but that only allows to cut your losses, not to fight the abuse, as it is only on a going-forward basis (I read this in an article, and jotted down a note, but I unfortunately cannot track down the source – you may be luckier, or cleverer).
Then I was contacted by the site administrator through my blog contact form (again I removed their information), who had read my question on the WordPress forum:
Your Name: ______
Your Email Address: ______
Your Website: ______
Your site is under a CC license. What’s the trouble in republishing your content?
Subject: Your license
Time: Thursday July 26, 2012 at 12:26 am
IP Address: ________
Contact Form URL: http://mycarta.wordpress.com/contact/
Sent by an unverified visitor to your site.
I responded with a polite letter, as suggested by @punkish on twitter. I explained why I thought they were exceeding what was warranted under the Creative Commons license, that republishing the About page and Sabbatical posts was to me proof of scraping, and I threatened to pursue legal recourse, starting with DMCA Notice of Copyright Infringement. Following my email they removed all my posts from their site, and notified me.
I think I was fortunate in this case, and decided to take matters into my own hands to prevent it from happening again. Following my research I saw two good, viable ways to better protect my blog from scraping whole content, while continuing to share my work. The first one involved switching to WordPress.org. This would allow more customization of the blog, and use of such tools as the WP RSS footer plugin, which allows to Get credit for scraped posts, and WP DMCA website protection. Another benefit of switching to WordPress.org is that – if you are of belligerent inclination – you can try to actively fight content scraping with cloacking. Currently, although it is one of my goals for the future of this blog, I am not prepared to switch WordPress.com due to time constraints.
Having decided to stick to WordPress.com the alternative I camu up with was to remove the CC license, replacing it with a Copyright notice with what I would call a liberal attitude. A simple way to do that was to add the Konomark logo accompanied by a statement that encourages sharing, but without surrendering any rights upfront. Addtionally you can prevent content theft from your WordPress.com (or at least reduce the risk) by configuring the RRS feed so that it displays post summaries only, not full posts.
How I share now
I customized my statement to reduce as much as possible the need for readers to ask for permission by allowing WorPress reblogging and by allowing completely open use of my published code and media. Below is a screen capture of my statement, which it is located in the blog footer:
I hope this will be helpful for those that may have the same problem. Let me know what you think.
Whine Journalism and how to bring the splashback – a great story and a great step-by-step guide, to fight content theft
Content Scrapers – How to Find Out Who is Stealing Your Content & What to Do About It
Useful tools to detect stolen content
Copyscape – Search for copies of your page on the web
TinEye - reverse image search engine. ‘It finds out where an image came from, how it is being used, if modified versions of the image exist…’