Post Creative Commons

AcaWiki

Tuesday, October 6th, 2009

AcaWiki† officiously launches tomorrow. The goal is to make academic knowledge more accessible through wiki community curated article “summaries” — something like long abstracts aimed at a general audience rather than specialists.

This could be seen as an end-run around access and copyright restrictions (the Open Access movement has made tremendous progress though there is still much to be done), but AcaWiki is a very partial solution to that problem — sometimes an article summary (assuming AcaWiki has one) would be enough, though often a researcher would still need access to the full paper (and the full dataset, but that’s another battle).

More interesting to me is the potential for AcaWiki summaries to increase the impact of research by making it more accessible in another way — comprehensible to non-specialists and approachable by non-speedreaders. I read a fair number of academic papers and many more get left on my reading queue unread. A “human readable” distillation of the key points of articles (abstracts typically convey next to nothing or are filled with jargon) would really let me ingest more.

Probably the closest things to AcaWiki summaries are Research Blogging and the idea that journal authors should contribute to Wikipedia. While both of these are great, blog posts don’t obtain the benefits (and costs) of distributed authoring and maintenance and direct contribution of research to Wikipedia has very limited applicability. So I think AcaWiki can make a big contribution. It could turn out that some granularity other than individual article summary is the sweet spot for community curation of academic knowledge — one could imagine field and sub-field and sub-sub-field surveys organized in WikiProject†† fashion as that — but article summaries are a very concrete place to begin, and more should naturally grow out of the AcaWiki community’s efforts to figure out the best ways to create and organize article summaries.

I’ve written a summary of Steven Levitt’s Why are Gambling Markets Organised So Differently from Financial Markets? I’d be really appreciative of article summaries in the following categories:

†I’ve been somewhat involved in AcaWiki over the past year — I’m on its board and Creative Commons has done some technology consulting on the project, credit to Nathan and bits from Steren, Nathan K, Alex and Parker — and note that Neeru Paharia, AcaWiki’s founder, was one of CC’s earliest employees. AcaWiki summaries are of course contributed under a CC Attribution license, so you can do anything you want with them so long as you link back to the summary.

††I urge anyone not already impressed by the contribution of WikiProjects on Wikipedia or generally interested in community curation and quality to check out Martin Walker’s WikiProjects: Improving Wikipedia by organising and assessing articles presented at Wikimania 2009.

The singularity university is open

Saturday, August 1st, 2009

Tuesday afternoon I visited ‘s graduate studies program to participate in a session on open source with (Google Open Source Program) and (WordPress). It was pretty interesting, though not in the way I expected — lots about contemporary licensing issues (which DiBona called roughly “the boring yet intellectually interesting part of his job”, a hilarious characterization in my book), not so much about how open source development will impact the future, nothing about an open source singularity. I sped through slides which include a scattershot of material for people interested in open source, a grand future, and not necessarily familiar with Creative Commons.

Hearing Mullenweg’s commitment to software freedom in person made me feel good about using WordPress. There was some discussion of network services and relatedly the . Mullenweg made a comment along the lines of silos like Facebook being less than ideal (not discussed, but , built on WordPress, as well as , used for SingularityU’s internal social network, are open replacements, though it seems to me that federation a la is needed).

DiBona indicated that Google doesn’t use AGPL’d software internally because it might cause them to share more than they’ve decided to (and they consciously decide to share a lot) while Mullenweg wondered whether complying with the AGPL would be difficult for WordPress deployers, including the question of whether one would need to share configuration files that include passwords. One could argue that such doubts are very self serving for Google and to a lesser extent WordPress.com (which use tons of free software and aren’t forced to share their improvements, though as mentioned, they both share lots), however, I hope that AGPL advocates (including me, with the caveat that I consider the importance of copyleft of whatever strength relative to release under any open license and non-licensing factors an open and understudied — consider possibilities for simulation, econ lab, and natural experiments — question, and I’m happy to change my mind) take them as strong signal that much more information on AGPL compliance is needed — sharing all source of a complex deployed web application is not often a simple thing.

Not explicitly but much more than tangentially related, probably the single most interesting thing said on the panel was Mullenweg saying that any internal WordPress.com developer can push changes to production at any time, and this happens 15-20 times a day, and he wishes he could do this for other deployments. My longstanding guess (not specific to WordPress) is that making deployment from revision control the preferred means of deployment would facilitate both more deployments running the latest changes as well as sharing their own.

I got a sense from questions asked by the students that the current Singularity University program might be more mainstream than the name implies. I understand that each student, or perhaps group of students, is to write a plan for using emerging technology to positively impact the lives of a billion people in one of the areas of health, climate change, or (I forgot the third area) in the next ten years. In any other context those parameters would sound very aggressive. Of course they could be met by first becoming rationalist jedi masters and then turning all available matter into . Alas, ten years is a hurdle.

If the previous paragraph reads snarkily, it is not — I fully support the maximization of computation and the rationality of the same. In any case congratulations to all involved in SingularityU, in particular Bruce Klein, who I know has been working on the concept for a long time. It was also good to see Salim Ismail and David Orban. I’m especially happy to see that SingularityU is attempting to be as open as possible, not least this.

Content layer infrastructure

Saturday, July 25th, 2009

Last Sunday I appeared (mp4 download) on a tech interview program called Press: Here. It went ok. Most of the questions were softball and somewhat repetitive. Lots more could have been said about any of them, but I think I did a pretty good job of hitting a major point on each and not meandering. However, one thing I said (emphasized below) sounds like pure bs:

this has been done in the open source software world for a couple decades now and now that people are more concerned about the content layer that’s really part of the infrastructure having a way to clear those permissions without the lawyer-to-lawyer conversation happen every single time is necessary

I could’ve omitted the bolded words above and retained the respect of any viewer with a brain. What the heck did I mean? I was referring to an argument, primarily made by Joi Ito over the last year or so, using a stylized version of the layers of a protocol stack. David Weinberger’s live-blogging of Ito provides a good summary:

Way back when, it was difficult to connect computers. Then we got Ethernet, then TCP/IP, and then HTTP (the Web). These new layers allow participation without permission. The cost of sending information and the cost of innovation have gone down (because the cost of failure has gone down). Now we’re getting another layer: Creative Commons. “By standardizing and simplifying the legal layer … I think we will lower the costs and create another explosion of innovation.”

Protocol geeks may object, but I think it’s a fairly compelling argument, at least for explaining why what Creative Commons does is “big”. The problems of not having a top layer (I called it “content”, the slide photographed above says “knowledge” — what it calls “content” is usually called “application”, and the note above says “legal”, referring to one required mechanism for opening up permissions around content, knowledge, or whatever one wishs to call it) in which a commons can be taken for granted (ie like infrastructure) is evident, for example in the failure by lawsuit of most interesting online music services, or the inaccessibility of much of the scientific literature to most humans and machines (eg for data mining), as are powerful hints as to what is possible where it exists, for example the vast ecology enabled by Wikipedia’s openness such as DBpedia.

I didn’t make that argument on-screen. Probably a good thing, given the previous paragraph’s tortured language. I shall practice. Critique welcome.

Press: Here is broadcast from its SF bay area home station (NBC) and I’ve heard is syndicated to many other stations. However, its website says nothing about how to view the program on TV, even on its home station. I even had a hard time finding any TV schedule on the NBC Bay Area website — a tiny link in the footer takes one to subpages for the station with lame schedule information syndicated from TV Guide. I found this near total disconnect between TV and the web a very odd, but then again, I don’t really care where the weird segment of the population that watches TV obtains schedule information. Press: Here ought to release its programs under a liberal CC license as soon as the show airs. Its own website gets very little traffic, many of the interviews would be relevant for uploading to Wikimedia Commons, and the ones that got used in Wikipedia would drive significant traffic back to the program website.

Conjectured impact of Wikipedia license interoperability?

Sunday, May 31st, 2009

Wikipedians voted overwhelmingly against kryptonite — for using Creative Commons Attribution-ShareAlike (CC BY-SA) as the main content license for Wikipedias and their sibling projects, permitting these to incorporate work offered under CC BY-SA, the main non-software copyleft license used outside of Wikipedia, and other CC BY-SA licensed projects to incorporate content from Wikipedia. The addition of CC BY-SA to Wikimedia sites should happen in late June and there is an outreach effort to encourage non-Wikimedia wikis under the Free Documentation License (FDL; usually chosen for Wikipedia compatibility) to also migrate to CC BY-SA by August 1.

This change clearly ought to over time increase the proportion of content licensed under free-as-in-freedom copyleft licenses. More content licensed under a single or interoperable copyleft licenses increases the reasons to cooperate with that regime — to offer new work under the dominant copyleft license (in the non-software case, now unambiguously CC BY-SA) in order to have access to content under that regime — and decreases the reasons to avoid copylefted work, one of which is the impossibility of incorporating works under multiple and incompatible copyleft licenses (when relying on the permissions of those licenses, modulo fair use). Put another way, the unified mass and thus gravitational pull of the copylefted content body is about to increase substantially.

Sounds good — but what can we expect from the actual impact of making legally interoperable the mass of Free Culture and its exemplar, Wikipedia? How can we gauge that impact, short of access to a universe where Wikipedians reject CC BY-SA? A few ideas:

(1) Wikimedia projects will be dual licensed after the addition of CC BY-SA — content will continue to be available under the FDL, until CC BY-SA content is mixed in, at which point the article or other work in question is only available under CC BY-SA. One measure of the licensing change’s direct impact on Wikimedia projects would be the number and proportion of CC BY-SA-only articles over time, assuming an effort to keep track.

I suspect it will take a long time (years?) for a non-negligible proportion of Wikipedia articles to be CC BY-SA-only, i.e., to have directly incorporated external CC BY-SA content. However, although most direct, this is probably the least significant impact of the change, and my suspicion could be upset if other impacts (below) turn out to be large, creating lots of CC BY-SA content useful for incorporating into Wikipedia articles.

(2) Content from Wikipedias and other Wikimedia projects could be incorporated in non-Wikimedia projects more. The difficulty here is measurement, but given academic interest in Wikipedia and the web generally, it wouldn’t be surprising to see the requisite data sets (historical and ongoing) and expertise brought together to analyze the use of Wikimedia project content elsewhere over time. Note that a larger than expected (there’s the rub) increase in such use could be the result of CC BY-SA being more straightforward for users than the FDL (indeed, a major reason for the change) as much or more than the result of license interoperability.

(3) New and existing projects could adopt or switch to CC BY-SA when they otherwise wouldn’t have in order to gain compatibility with Wikimedia projects. One sure indication of this would involve major projects using a CC license with a “noncommercial” term switching to CC BY-SA and giving interoperability with Wikipedia as the reason for the switch. Another indicator would simply be an increase in the use of CC BY-SA (and even more permissive instruments such as CC BY and CC0, to the extent the motivation is primarily to create content that can be used in Wikipedia rather than to use content from Wikipedia) relative to more restrictive (and non-interoperable with Wikipedia) licenses.

(4) Apart from needing to be compatible with Wikipedia because one desires to incorporate its content, one might want to be compatible with Wikipedia because it is “cool” to be so. I don’t know that this has occurred on a significant scale to this date, so if it begins to one possible factor in such a development would be the change to CC BY-SA. How could this be? As cool as Wikipedia compatibility sounds, having to adopt a hard to understand license intended for software documentation (the FDL) makes attaining this coolness seem infeasible. Consideration of the FDL just hasn’t been on the radar of many outside of the spaces of documentation, encyclopedias, and perhaps educational materials, while consideration and oftentimes use of CC licenses is active in many segments. However, in most of these more restrictive CC licenses (i.e., those prohibiting commercial use or adaptation) are most popular. So if we see an upsurge in the use of CC BY-SA for popular culture works (music, film) the beginning of which coincides with the Wikimedia licensing change, it may not be unreasonable to guess that the latter caused the former.

(5) The weight of Wikipedia and relative accessibility of CC BY-SA could further consensus that the freedoms demanded by Wikimedia projects are some combination of “good”, “correct”, “moral”, and “necessary” — if some of these can be distinguished from “cool”. In the long term, this could be indicated by the sidelining of terms for content that do not qualify as free and open, as they have been for software, where and similar obvious competitors for important free software niches are strategically irrelevant.

Obviously 3, 4, and 5 overlap somewhat.

(6) I conjecture that making more cultural production more wiki-like (or to gain WikiNature) is probably the biggest determinant of the success of Free Culture. More interplay between the Wikipedia, both the most significant free culture project and the most significant wiki, and the rest of the free culture and open content universe can only further this trend — though I have no idea how to measure the possible impact of the licensing change here, and wouldn’t want to ascribe too much weight to it.

(7) Last, the attention of the Wikipedia community ought to have a positive impact on the quality of future versions of Creative Commons licenses (there shouldn’t be another version until 2011 or so, and hopefully there won’t be another version after that for much longer). Presumably Wikipedians also would have had a positive impact on future versions of the FDL, but arguably less so given the Free Software Foundation’s (excellent) focus on software freedom.

Will any of the above play out in a significant way? How much will it be reasonable to attribute to the license change? Will researchers bother to find out? Here’s to hoping!

Prior to the Wikipedia community vote on adopting CC BY-SA it crossed my mind to set up several play money prediction market contracts concerning the above outcomes conditioned on Wikipedia adopting CC BY-SA by August 1, 2009, for which I did set up a contract. It is just as well that I didn’t — or rather if I had, I would have had to heavily promote all of the contracts in order to stimulate any play trading — the basic adoption contract at this point hasn’t budged from 56% since the vote results were announced, which means nobody is paying attention to the contract on Hubdub.

Wikipedians against kryptonite

Monday, April 13th, 2009



As mentioned previously incompatible widely used copyleft licenses are kryptonite to the efficacy of copyleft. If you’ve made 25 or more edits* to a Wikimedia project, you can vote to liberate Wikipedia from this kryptonite. Vote now, instructions and much more background on the Creative Commons blog.


Original poster by Brianna Laugher / CC BY

* My favorite interview question for any position at Creative Commons goes something like “tell me about your experiences with editing Wikipedia” which serves the dual purposes of testing whether the candidate knows how to use a computer (you’d be surprised) and has any practical clue about the types of collaboration Creative Commons’ work facilitates.

Happy Hacking

Wednesday, March 25th, 2009

Laroia, Linksvayer, RMS
Asheesh Laroia and Mike Linksvayer of Creative Commons accept the 2008 Free Software Foundation Award for Project of Social Benefit from Richard Stallman. Detail of photo by Matt Hins / CC BY-SA.



Icing on the cake of a highly successful Libre Planet Conference. Other highlights included great talks by Evan Prodromou on engineering for free network services and Rob Savoye on , which turns out to be much more than just an Adobe Flash browser plugin replacement, and the free network services unconference.

Addendum 20090330: Audio of Stallman’s talk and the awards ceremony, Asheesh’s writeup.

Free Software: Foundation for a Libre Planet

Wednesday, February 4th, 2009

Support the Free Software Foundation. It’s good for a free planet and you can attend the just announced Libre Planet Conference, March 21-22 in Cambridge, Massachusetts, an outgrowth of the FSF’s annual member meeting.

I’m really excited that the conference will have software freedom and network services as a major focus. This will be the first public conference on the topic, following last year’s meeting from which followed the Franklin Street Declaration and Autonomo.us.

If you enjoyed my rambling call to support Creative Commons a couple months ago, you might enjoy reading Benjamin Mako Hill’s somewhat less rambling call to support the FSF.

I’ve donated to the FSF off and on since at least 1998. You should get started now, if you haven’t already. My only regret (apart from not giving every year) is still not having relevant prediction markets enabling me to be a futarchist donor. I mention that here both because it is a necessary disclaimer for me to make (my philanthropy suggestions are not based on handwaving, not consensus projected impact) and because perhaps my most highly desired free network service is a prediction market exchange. I’ll explain more another day.

Goodbye 20th Century: A Biography of Sonic Youth

Sunday, January 4th, 2009

begins Goodbye 20th Century: A Biography of Sonic Youth very inauspiciously. On page 1 he relates not knowing noise was an “iTunes category” and never having seen the designation unclassifiable before researching the book. I almost had to put the book down without turning to page 2 — was Browne a liar or a total ignoramus?

After mercifully brief attempted introductions (the genre discovery story above is the first of seven) to the book, Browne spends about 390 pages relating the nuts and bolts of Sonic Youth’s prehistory and history through about 2006. If you aren’t a big Sonic Youth fan, just skim instead of reading this book.

Sonic Youth was my last singular favorite band. I’ve probably listened to their music for thousands of hours, mostly during 1988-1998 (and mostly their music released from 1982-1995). I still try to see them when I can, most recently performing all of Daydream Nation live in Berkeley (a review on what looks like a nice blog) and Thurston Moore’s solo rock project at Amoeba Records and Great American Music Hall, all in 2007, and by far the best, Kim Gordon with Ikue Mori, Zeena Parkins, Trevor Dunn, and Yoshimi at Montalvo Arts last year. So that’s why I stuck with the book.

I learned a few things from the book — I knew the names and sequence of all of the group’s drummers, but didn’t realize how chaotic that sequencing was; I didn’t realize that Moore played with Glenn Branca’s ensembles after Sonic Youth started, not before; nor that Lee Ranaldo came close to leaving the group at one point. I already knew that some members of the group have a pop culture fascination, though it is always sad to see that confirmed in anyone.

Browne writes a fair amount about the band’s business, the success of which is pretty marginal, with one distantly related exception — Gordon received close to $500,000 for her half of X-Girl, a fashion company she co-founded that became popular in Asia (page 319). Sonic Youth’s first three major label albums (released in 1990, 1992, and 1994) first year sales were under 200k, nearly 300k, and nearly 250k respectively (pages 259 and 277). Subsequent (and previous) albums all sold under 100k copies, though I’d have to guess Daydream Nation (1988) has racked up considerably more than that over the past 20 years given its classic status.

I’ll guesstimate that the band has sold 2 million albums over its 26 year history. Given the approximation that artists make $1.60 on each album, Sonic Youth has made only $3.2 million on album sales, or about $120k/year, or $30k/year/band member — in New York City for almost their entire history.

Unsurprisingly live shows have remained their leading source of income (page 386), and through most of their artistically most interesting period (the beginning through 1988, in my opinion) they worked day jobs (pages 151 and 179).

Browne mentions many times the band’s frugality and nearly complete lack of stereotypical rock and roll lifestyles. Presumably this has been important in keeping them together for so long and keeping them creative — although I said above that I consider their early work their most interesting, their subsequent work as a band is still very good, and many of their individual projects continue to be amazing.

Mostly because I love Sonic Youth, I’ve long daydreamed about them doing something with Creative Commons. In 2005 Moore published a column in WIRED that concluded with this:

Once again, we’re being told that home taping (in the form of ripping and burning) is killing music. But it’s not: It simply exists as a nod to the true love and ego involved in sharing music with friends and lovers. Trying to control music sharing – by shutting down P2P sites or MP3 blogs or BitTorrent or whatever other technology comes along – is like trying to control an affair of the heart. Nothing will stop it.

5 years of posts as wordles

Saturday, January 3rd, 2009

Composition of wordles / CC BY

Unsatisfying, or perhaps this blog is just that uninteresting. Code used to produce yearly wordlists. Some possible improvements:

  • Rewrite as WordPress plugin OR abstract from WordPress
  • Case insensitivity
  • Suppress common words (used Wordle menu for this, but it isn’t very aggressive), perhaps using a word frequency dataset
  • Use free software alternative to Wordle to generate wordclouds (suggestions?)
  • Automate generation of wordclouds (very difficult using Wordle, would involve browser automation, thus previous bullet)

I started doing this in part to see five years of topic changes on this blog, but mostly because if it worked well, I’d use it on the Creative Commons blog, which is a 6+ year mass of around 2,500 almost completely uncategorized/untagged posts. In that vein, I intend to look into automated term extraction and user tagging code.

CC6+

Wednesday, December 17th, 2008

December 16 marked six years since the release of the first Creative Commons licenses. Most of the celebrations around the world have already taken place or are going on right now, though San Francisco’s is on December 18. (For CC history before 2002-12-16, see video of a panel recorded a few days ago featuring two of CC’s founding board members and first executive director or read the book Viral Spiral, available early next year, though my favorite is this email.)

I’ve worked for CC since April, 2003, though as I say in the header of this blog, I don’t represent any organization here. However, I will use this space to ask for your support of my and others’ work at CC. We’re nearing the end of our fourth annual fall public fundraising campaign and about halfway to our goal of raising US$500,000. We really need your support — past campaigns have closed out with large corporate contributions, though one has to be less optimistic about those given the financial meltdown and widespread cutbacks. Over the longer term we need to steadily decrease reliance on large grants from visionary foundations, which still contribute the majority of our funding.

Sadly I have nothing to satisfy a futarchist donor, but take my sticking around as a small indicator that investing in Creative Commons is a highly leveraged way to create a good future. A few concrete examples follow.

became a W3C Recommendation on October 14, the culmination of a 4+ year effort to integrate the Semantic Web and the Web that everyone uses. There were several important contributors, but I’m certain that it would have taken much longer (possibly never) or produced a much less useful result without CC’s leadership (our motivation was first to describe CC-licensed works on the web, but we’re also now using RDFa as infrastructure for building decoupled web applications and as part of a strategy to make all scientific research available and queryable as a giant database). For a pop version (barely mentioning any specific technology) of why making the web semantic is significant, watch Kevin Kelly on the next 5,000 days of the web.

Wikipedia seems to be on a path to migrating to using the CC BY-SA license, clearing up a major legal interoperability problem resulting from Wikipedia starting before CC launched, when there was no really appropriate license for the project. The GNU FDL, which is now Wikipedia’s (and most other Wikimedia Foundation Projects’) primary license, and CC BY-SA are both copyleft licenses (altered works must be published under the same copyleft license, except when not restricted by copyright), and incompatible widely used copyleft licenses are kryptonite to the efficacy of copyleft. If this migration happens, it will increase the impact of Wikipedia, Creative Commons, free culture, and the larger movement for free-as-in-freedom on the world and on each other, all for the good. While this has basically been a six year effort on the part of CC, FSF, and the Wikimedia Foundation, there’s a good chance that without CC, a worse (fragmented, at least) copyleft landscape for creative works would result. Perhaps not so coincidentally, I like to point out that since CC launched, there has been negative in the creative works space, the opposite of the case in the software world.

Retroactive copyright extension cripples the public domain, but there are relatively unexplored options for increasing the effective size of the public domain — instruments to increase certainty and findability of works in the public domain, to enable works not in the public domain to be effectively as close as possible, and to keep facts in the public domain. CC is pursuing all three projects, worldwide. I don’t think any other organization is placed to tackle all of these thorny problems comprehensively. The public domain is not only tremendously important for culture and science, but the only aesthetically pleasing concept in the realm of intellectual protectionism (because it isn’t) — sorry, copyleft and other public licensing concepts are just necessary hacks. (I already said I’m giving my opinion here, right?)

CC is doing much more, but the above are a few examples where it is fairly easy to see its delta. CC’s Science Commons and ccLearn divisions provide several more.

I would see CC as a wild success if all it ever accomplished was to provide a counterexample to be used by those who fight against efforts to cripple digital technologies in the interest of protecting ice delivery jobs, because such crippling harms science and education (against these massive drivers of human improvement, it’s hard to care about marginal cultural production at all), but I think we’re on the way to accomplishing much more, which is rather amazing.

More abstractly, I think the role of creating “commons” (what CC does and free/open source software are examples) in nudging the future in a good direction (both discouraging bad outcomes and encouraging good ones) is horribly underappreciated. There are a bunch of angles to explore this from, a few of which I’ve sketched.

While CC has some pretty compelling and visible accomplishments, my guess is that most of the direct benefits of its projects (legal, technical, and otherwise) may be thought of in terms of lowering transaction costs. My guess is those benefits are huge, but almost never perceived. So it would be smart and good to engage in a visible transaction — contribute to CC’s annual fundraising campaign.