My Open Licensing Journey

Today, I relicensed all of my photos on Flickr from CC BY-NC-SA to CC BY. In English, that means that you may reuse, redistribute, remix, and even resell any of my Flickr photos as long as you give me credit.

I’ve been meaning to do this for a long time, but hadn’t, mostly due to laziness. Flickr has a batch relicensing feature, but it failed on my 12,000 photos, so I had to do this mostly manually, which was a pain. I also plan on embedding the license in the pictures themselves from this point forward using Jeffrey Friedl’s Creative Commons Lightroom plugin. I had already done this for my Instagram photos using Philip Neustrom’s clever service, i-am-cc.org.

Why now? It was some combination of me working on my photography workflow today, thinking about licensing for Faster Than 20, and thinking about Aaron Swartz, who died one year ago.

Why do this at all? In general, I’m trying to make the world a better place. I believe that sharing my knowledge artifacts can help with that, but others need to be able to reuse that knowledge. The fewer barriers I create, the easier it is for others to do that. I also believe that doing this is better for me financially, that I am likely to make more money over time by giving away my knowledge than I would by trying to restrict it.

I’ve always been a strong advocate for open licensing, and I’ve always favored less restrictive licenses in theory. But when I first had to choose a license for my photos, I hedged, and I placed a “non-commercial, share-alike” restriction.

In practice, this has worked swimmingly for me. The only problem I’ve had is that non-commercial licenses are incompatible with Wikimedia. When I’ve wanted to upload content to Wikimedia Commons, or when someone has requested that I do, I’ve simply relicensed those particular pictures. That’s worked fine, but it hasn’t been ideal, and I’ve been wanting to get more active on Commons recently, which is a large part of why I’ve been wanting to relicense my content.

My reasons for relicensing, however, run much deeper than these minor roadblocks. It represents my ongoing journey of getting comfortable with giving up control, which speaks to where I am with Faster Than 20’s licensing.

I have long enjoyed the merits of open licensed content, and I’ve always been comfortable licensing my content that way. I’m not naive about the downsides. About a year after I published my first book (in 1996, predating Creative Commons by five years), I found a pirated version on the Internet. I would have been fine with that — it hadn’t sold well, and I wanted people to have access to the content — except that this person had replaced my name with his.

Even after I started open licensing everything, I’ve seen plenty of my content repurposed in ways that violate the already liberal licensing terms. I never feel great about it, but I the benefits have far outweighed the downsides, and it’s not like others have made millions off of my content.

Still, it takes a bit of faith to trust that the upsides will far outweigh the downsides. Over time, I’ve gotten more comfortable with this, and I’m wanting to be more liberal with my licenses.

My current thinking is to license all written content published on Faster Than 20 as CC0 — essentially public domain. In other words, I would be giving up all copyright and all associated rights for content written on Faster Than 20. I would accompany the license with a statement of how I’d like people to engage with the content, but I won’t require it.

I’ve been particularly persuaded by what Mike Linksvayer has been writing about CC0 and the whole suite of new CC licenses. At minimum, I’d like attribution, but who am I kidding? People attribute because they think it’s the right thing to do, not because they’re worried about me coming after them. I can be more explicit and more effective about what I want by inviting people rather than by relying on a license.

Why not release my photos under a CC0 license also? I could blame it on Flickr not offering that option (Flickr’s support for CC-licensed content is seriously lagging), but the reality is that I don’t want to. With pictures, I not only have a responsibility to myself, but also to my subjects. I’m not ready to give up all copyright and renouncing all control.

Fighting WikiSpam: Eaton and Shared Blacklists

WikiSym 2005 was awesome. Massive props to Dirk Riehle and the program committee for throwing an outstanding event and drawing tons of great, great people. With Wikimania last August and WikiSym this past week, the Wiki community is really starting to gel. And it’s about time. Can you believe Wikis are 10 years old?    (JXD)

Now the bad news: I walked away with some action items. How do I get myself into these messes?!    (JXE)

The first action item can be traced back to an ad hoc meeting that happened at Wikimania regarding WikiSpam. On August 6, a group of Wiki developers — me (PurpleWiki), Alex Schroeder (OddMuse), Brion Vibber (Mediawiki), Thomas Waldmann (MoinMoin), Sven Dowideit (TWiki), Janne Jalkanen (JSPWiki) — along with John Breslin and Jochen Topf, got together to discuss ways we could collaborate on fighting WikiSpam. Our goal was to identify the simplest possible first step and not to get mired in process discussions.    (JXF)

Since all of us were already maintaining URL blacklists, we decided to merge them and host it as a Sourceforge project. We agreed on a standard format (which I’ll document and post soon), and we agreed to send our respective lists to Alex, who already has scripts to slice, dice, and merge.    (JXG)

One of my action items then was to create the Sourceforge project. I did that immediately, but for some reason, the project was rejected. Thus began a month-long go-around with Sourceforge support where I tried to discover why they had rejected the proposal. In the end, the project was approved, and I never got an answer as to why it was rejected in the first place. At that point, I was mired in other work, and so I never followed up.    (JXH)

WikiSym was the kick in the butt I needed to follow-up. On Sunday, Sunir Shah hosted an antispam workshop, which about 40 people attended. First, Sunir reviewed techniques (many of which are listed at MeatBall:WikiSpam). Then we broke out.    (JXI)

In my breakout, I described what we had agreed on at Wikimania. Then Peter Kaminski described a very cute idea he had for making it easy to fight WikiSpam. In a nutshell, Peter suggested we write a simple drop-in replacement CGI wrapper that would filter a POST payload for spam and call the real CGI script — be it a Wiki, a blog, or anything else — if the payload were spam-free. Such a wrapper would enable users to install spam-protection for any CGI script without having to write a single line of code and without having to do any complex configuration. It wouldn’t require any special access to your web server, since it would just be a CGI script. And you could easily add other spam-fighting measures, such as throttling and IP blacklists.    (JXJ)

I thought it was a brilliant idea. So Peter and I sat down afterwards and whipped it up. Took about an hour. It’s called Eaton, it works, and it’s Public Domain. Peter Kaminski has already blogged about it, and there’s some important commentary there from Jay Allen, the creator of MT-Blacklist.    (JXK)

It’s a proof of concept, and it won’t scale. It can and should be improved, and I’d encourage folks to do so. Nevertheless, it’s pretty cool. Bravo to Peter for a very clever idea.    (JXL)

By the way, the first person to figure out the origins of the name “Eaton” wins a cookie.    (JXM)