Post Creative Commons

Novakick

Wednesday, July 27th, 2011

I backed Novacut’s first, unsuccessful, Kickstarter campaign last year because I think that new tools for distributed collaborative creation and curation are important to the success of free culture (which I just said is a lame name for intellectual freedom, but I digress) and Novacut’s description seemed to fit the bill:

We’re developing a free open-source video editor with a unique distributed design:

  • Distributed workflow – collaboratively edit video with other artists over the Internet
  • Distributed storage – seamlessly store and synchronize video files across multiple computers and the cloud
  • Distributed rendering – seamlessly spread rendering and encoding across multiple computers and the cloud

I didn’t investigate whether Novacut had a feasible plan. My pledge was an expressive vote for the concept of new tools for distributed collaboration.

Novacut is making another go of it at Kickstarter, and it looks like they’ll succeed. I just pledged again.

However, I’m saddened by how much of philanthropy is not also carefully instrumental. The only low barrier way to move in this direction (I’d prefer futarchist charity) that I know of is criticism, so hats off to Danny Piccirillo for his criticism of Novacut fundraising. I’m further saddened that such criticism is not welcomed. I would be honored that someone found a project I am involved in or a fan of worth the time to criticize and thankful for the free publicity.

Now, I’m looking forward to see what Novacut delivers, and/or what Novacut ideas other video editor projects implement.

Speaking of delivery, I noticed today a new crowdfunding site targeting free software and Brazil, makeITopen. According to a writeup, it appears to have a couple interesting twists. Projects that do not reach their thresholds have donations not fully returned to donors, but only as credits within the system (unlike Kickstarter and others, where pledges are not collected until a project has reached its threshold). More interestingly, there is a process for donors to approve (or not) the software delivered by the project. This sort of thing is probably hard to get right, and I fully expect makeITopen to fail, but I hope it is hugely successful, and think that getting approval right could be very useful. At least for donors who wish to be instrumental.

Addendum 20110730: The best two comments on the Novacut criticism kerfuffle: Jono Bacon saying be calm, but onus is on Novacut to explain, and Jason Gerard DeRose (Novacut lead), explaining how Novacut’s intended high-end userbase demands a different program than do casual video editors, and that there’s plenty of scope for cooperation on underlying components. Congratulations to Novacut for meeting its Kickstarter threshold, and good luck to Novacut, (the working editor many critics advocated directing resources toward), and and Gnonlin (two underlying components in common). Onward to killing King Kong with FLOSS.

Creative Commons hiring CTO

Monday, July 11th, 2011

See my blog post on the CC site for more context.

Also thanks to Nathan Yergler, who held the job for four years. I really miss working with Nathan. His are big shoes to fill, but also his work across operations, applications, standards, and relationships set the foundation for the next CTO to be very successful.

Semantic ref|pingback for re-use notification

Sunday, May 15th, 2011

Going back probably all the way to 2003 (I can’t easily pinpoint, as obvious mail searches turn up lots of hand-wringing about structured data in/for web pages, something which persists to this day) people have suggested using something like trackback to notify that someone has [re]used a work, as encouraged under one of the Creative Commons licenses. Such notification could be helpful, as people often would like to know someone is using their work, and might provide much better coverage than finding out by happenstance or out-of-band (e.g., email) notification and not cost as much as crawling a large portion of the web and performing various medium-specific fuzzy matching algorithms on the web’s contents.

In 2006 (maybe 2005) Victor Stone implemented a re-use notification (and a bit more) protocol he called the Sample Pool API. Several audio remix sites (including ccMixter, for which Victor developed the API; side note: read his ccMixter memoir!), but it didn’t go beyond that, probably in part because it was tailored to a particular genre of sites, and another part because it wasn’t clear how to do correctly, generally, get adoption, sort out dependencies (see hand-wringing above), and resource/prioritize.

I’ve had in mind to blog about re-use notification for years (maybe I already have, and forgot), but right now I’m spurred to by skimming Henry Story and Andrei Sambra’s Friending on the Social Web, which is largely about semantic notifications. Like them, I need to understand what the OStatus stack has to say about this. And I need to read their paper closely.

Ignorance thusly stated, I want to proclaim the value of refback. When one follows a link, one’s user agent (browser) often will send with the request for the linked page (or other resource) the referrer (the page with the link one just followed). In some cases, a list of pages linking to one’s resources that might be re-used can be rather valuable if one wants to bother manually looking at referrers for evidence of re-use. For example, Flickr provides a daily report on referrers to one’s photo pages. I look at this report for my account occasionally and have manually populated a set of my re-used photos largely by this method. This is why I recently noted that the (super exciting) MediaGoblin project needs excellent reporting.

Some re-use discovery via refback could be automated. My server (and not just my server, contrary to Friending on the Social Web; could be outsourced via javascript a la Google Analytics and Piwik) could crawl the referrer and look for structured data indicating re-use at the referrer (e.g., my page or a resource on it is subject or object of relevant assertions, e.g., dc:source) and automatically track re-uses discovered thusly.

A pingback would tell my server (or service I have delegated to) affirmatively about some re-use. This would be valuable, but requires more from the referring site than merely publishing some structured data. Hopefully re-use pingback could build upon the structured data that would be utilized by re-use refback and web agents generally.

After doing more reading, I think my plan to to file the appropriate feature requests for MediaGoblin, which seems the ideal software to finally progress these ideas. A solution also has obvious utility for oft-mooted [open] data/education/science scenarios.

DRM as a competitive threat to free software?

Wednesday, May 4th, 2011

A Day Against DRM post. I posted another at Creative Commons.

Critiques of Digital Restrictions Management fall into about 10 categories:

  1. DRM causes various product defects
  2. DRM usurps people’s control of devices they own
  3. DRM discourages tinkering and understanding technology
  4. DRM discourages sharing
  5. DRM curtails various freedoms people would otherwise enjoy
  6. DRM encourages hostile behavior toward consumers
  7. DRM encourages monopoly
  8. DRM is technical voodoo
  9. DRM is business voodoo
  10. DRM presages more forms of attempted control, each with additional properties similar to those above, increasing the probability of a dystopian future.

Eventually I may link the above bullets to the relevant posts on DRM I’ve made over the years.

Defective By Design, a project of the Free Software Foundation, coordinates the Day Against DRM and various other anti-DRM actions. It is pretty clear that several of the problems with DRM listed above, particularly 2-5, are inimical to the FSF’s values. I sometimes think the linkage to core values of software freedom could be made stronger in anti-DRM campaigns, but these are not easily packaged messages. I also think there’s usually a missed opportunity in anti-DRM campaigns to present free software (and maybe free culture) as the only systemic alternative to creeping anti-freedom technologies such as DRM.

I began writing a post for Day Against DRM because I wanted to pose a question concerning DRM’s competitive threat to free software: how significant is it in today’s circumstances, and how significant in theory?

In today’s circumstances, the use of DRM that does not support free software platforms by popular media services (currently Netflix is probably most significant; DVDs with DRM have always been a problem) seems like a major barrier to more people using free software.

In theory, it isn’t clear to me that DRM must be a competitive threat to free software adoption (though it would remain a threat to software freedom and nearby). If a mostly free software platform were popular enough, DRM implementations will follow — most obviously Android.

However, I would also hope the dominance of free software would create conditions in which DRM is less pertinent. I would love to see enumerated and explored the current and in-theory competitive threats to free software posed by DRM, and vice versa.

Notability, deletionism, inclusionism, ∞³

Tuesday, January 4th, 2011

For the past couple years there has been an in English Wikipedia (archived version). It is an ok article. Some that I’d include isn’t, and some of what is seems kind of tangential, e.g., talking at a NASA event, that besides a citation, netted spending the day with an unholy mix of the usual social media suspects and entirely retrograde “we gotta put man humans into space because it makes me feel proud to be an American and my daughter might do her math homework!!!” boosters (get real: go robots!) and a sketch. However, overall it is fairly evocative, even the NASA event part. It would be uncool of me to edit it directly, and I’ve been curious to see how it would be improved, translated, vandalized, or deleted, so I haven’t made suggestions. It has mostly just sat there, though it has been curious to see the content copied in various places where Wikipedia content gets copied, and that a fair proportion of the people I meet note that I “have a Wikipedia page” — that’s kind of the wrong way to think about it (Wikipedia articles have subjects, not owners), but good to know that people can use web search (and that I can tend toward the pedantic).

!#@!@^% deletionists are ruining Wikipedia. They’ll be the first against the wall when the revolution comes.
http://memesteading.com/2010/03/15/dialectical-inclusionism/

The one thing that I have said about the article about me on English Wikipedia, until now, has been this, on my (not precisely, but moreso “mine”) user page on English Wikipedia: “I am the subject of Mike Linksvayer, which I would strongly advocate deleting if I were a deletionist (be my guest).” I’ve thought about pulling some kind of stunt around this, for example, setting up a prediction market contract on whether the article about me would be deleted in a given timeframe, but never got around to it. Anyway, last week someone finally added an Articles for Deletion notice to the article, which sets up a process involving discussion of whether the article ought be deleted (crickets so far). When rough consensus is reached, an admin will delete the article, or the notice will be removed.

I’m not a fan of deletionism (more below), but given the current rules around notability, I am either somewhat questionable as an English Wikipedia article subject (using the general, easy to interpret charitably summary of notability: “A person is presumed to be notable if he or she has received significant coverage in reliable secondary sources that are independent of the subject.”) to unquestionably non-notable (any less charitable interpretation, which presumably any “deletionist” would use, thus my user page statement). The person who added the Articles for Deletion notice may not have done any research beyond what is already linked in the article (more on that general case below), but I must admit, his critique of the citations in the article, are fairly evocative, just as the article is:

We have three sources from Creative Commons (primary), a paragraph in a CNET news article where he does his job and encourages scientists to use CC licenses, one IHT article about veganism that mentions him for a couple of paragraphs, and a link to his Wikipedia userpage. That is not enough for notability, in my opinion.

The IHT (actually first in the NYT) article was about calorie restriction, not veganism, but that’s a nitpick. Most of the “media” items my name has appeared in are indeed about Creative Commons, i.e., me doing my job, not me as primary subject, or in a few cases, about calorie restriction, with me as a prop. Or they’re blogs — ok that one is even less notable than most blogs, but at least it’s funny, and relevant — and podcasts. The only item (apart from silly blog posts) that I’ve appeared in that I’m fond of and would be tickled if added as a reference if the current article about me squeaks by or some future article in the event I as a subject become a no-brainer (clearly I aim to, e.g., “[make] a widely recognized contribution that is part of the enduring historical record in his or her specific field”, but even more clearly I haven’t achieved this) is in Swedish (and is still about me doing my job, though perhaps going off-message): check out an English machine translation.

I’m not a fan of deletionism, largely because, as I’ve stated many times, thinking of Wikipedias as encyclopedias doesn’t do the former justice — Wikipedia has exploded the “encyclopedia” category, and that’s a wonderful thing. Wikipedias (and other Wikimedia projects, and projects elsewhere with WikiNature) need to go much further if freedom is to win — but I’m partisan in this, and can appreciate that others appreciate the idea that Wikipedias stick close to the category defined by print encyclopedias, including strong limits on what might be considered encyclopedic.

It also strikes me that if Wikimedia movement priorities include increasing readership and participation that inclusionism is the way to go — greatly increase the scope of material people can find and participate in building. However, I’m not saying anything remotely new — see Deletionism and inclusionism in Wikipedia.

Although I’m “not a fan” I don’t really know how big of a problem deletionism is. In my limited experience, dealing with an Articles for Deletion notice on an article I’ve contributed to is a pain, sometimes motivates substantially improving the article in question, and is generally a bummer when a useful, factual article is deleted — but it isn’t a huge part of the English Wikipedia editing experience.

Furthermore, reading guidelines on notability closely again, they’re more reasonable than I recall — that is, very reasonable, just not the radical inclusionism I prefer. To the extent that deletionism is a problem, my guess now is that it could be mitigated by following the guidelines more closely, not loosening them — start with adding a {{notability}} tag, not an Articles for Deletion notice, ask for advice on finding good sources, and make a good faith effort to find good sources — especially for contemporary subjects, it’s really simple with news/web/scholar/book/video search from Google and near peers. I’m sure this is done in the vast majority of cases — still, in the occasional case when it isn’t done, and initial attempts to find sources and improve an article are being made during an Articles for Deletion discussion, is kind of annoying.

I also wrote some time ago when thinking about notability the not-to-be-taken-very-seriously Article of the Unknown Notable, which I should probably move elsewhere.

The delicious “dialectical inclusionism” quote above is from Gordon Mohr. Coincidentally, today he announced ∞³, a project “to create an avowedly inclusionist complement to Wikipedia”. There’s much smartness in his post, and this one is already long, so I’m going to quote the entire thing:

Introducing Infinithree (“∞³”)

Wikipedia deletionism is like the weather: people complain, but nobody is doing anything about it. 

I’d like to change that, working with others to create an avowedly inclusionist complement to Wikipedia, launching in 2011. My code name for this project is ‘Infinithree’ (‘∞³’), and this blog exists to collaborate on its creation.

Why, you may ask?

I’ll explain more in future posts – but in a nutshell, I believe deletionism erases true & useful reference knowledge, drives away contributors, and surrenders key topics to cynical spammy web content mills.

If you can already appreciate the value and urgency of this sort of project, I’m looking for you. Here are the broad outlines of my working assumptions:

Infinithree will use the same open license and a similar anyone-can-edit wiki model as Wikipedia, but will discard ‘notability’ and other ‘encyclopedic’ standards in favor of ‘true and useful’.

Infinithree is not a fork and won’t simply redeploy MediaWiki software with inclusionist groundrules. That’s been tried a few times, and has been moribund each time. Negative allelopathy from Wikipedia itself dooms any almost-but-not-quite-Wikipedia; a new effort must set down its roots farther afield.

Infinithree will use participatory designs from the social web, rather than wikibureacracy, to accrete reliable knowledge. Think StackOverflow or Quora, but creating declarative reference content, rather than interrogative transcripts.

Sound interesting? Can you help? Please let me know what you think, retweet liberally, and refer others who may be interested.

For updates, follow @_infinithree on Twitter (note the leading underscore) or @infinithree on Identi.ca.

Infinithree is already very interesting as a concept, and I’m confident in Gordon’s ability to make it non-vapor and extremely interesting (I was one of his co-founders at the early open content/data/mass collaboration service Bitzi — 10 years ago, hard to believe). There is ample opportunity to try different mass collaboration arrangements to create free knowledge. Many have thought about how to tweak Wikipedia culture or software to produce different outcomes, or merely to experiment (I admit that too much of my plodding pondering on the matter involves the public domain↔strong copyleft dimension). I’m glad that Gordon intends ∞³ to be different enough from Wikipedia such that more of the vast unexplored terrain gets mapped, and hopefully exploited. As far as I know is probably the most relevant attempt so far. May there be many more.

Dear Jean Quan,

Sunday, January 2nd, 2011

Congratulations on your election and tomorrow’s inauguration as Oakland mayor.

I ranked ahead of you, but in truth my expressive rationale for doing so could just as well have favored you: a progressive Asian American woman represents a defining characteristic of what makes Oakland special and its future just as much as does a green lesbian (who is also an American and a woman, but such is identity politics).

Expressiveness aside, expectations for positive outcomes from your term as mayor are pretty low (note emphasis on outcomes; everyone knows you’ll put in more hours than recent Oakland mayors). Oakland still has a terrible crime problem, and city finances are beyond terrible. I suspect if there were betting markets on outcomes related to these problems, current prices would predict that under your leadership crime will get worse (relative to comparable cities; of course national trends may determine absolute direction of change), chief police will quit, the city will teeter on bankruptcy, your response will be to ‘social program us to death’, and you will be a one term mayor, succeeded by Kaplan, Joe Tuman, or .

Low expectations can be a blessing, if you’re willing to take steps to smash them and secure your re-election and legacy as Oakland’s most successful mayor in decades.

First, crime. Blaming the problem on poverty, racism, poor schools, unemployment, etc., isn’t going to cut it, neither as discourse nor as the stereotypical actions resulting, loosely characterized as “building youth centers”. Most voters aren’t that stupid (well, they are, but in other directions when it comes to crime). Fortunately, one can be a good progressive, acknowledge that crime is a major problem, especially for the disadvantaged, and take smart, progressive-compatible steps to smash crime. Check out Progressive Change Campaign Committee co-founder Aaron Swartz’s essay on crime:

Such things are a frustration for white suburbanites, but for poor people stuck in the ghetto, they’re a nightmare. Crime is yet another disadvantage and a particularly noxious one at that. Even aside from all the other indignities suffered by the poor, just imagining life in a crime-ridden neighborhood is enough to make your skin crawl.

So there’s the question: How can we have less crime with less punishment?

Here are the no-brainer steps you can take on crime:

  • Do not get caught saying anything that could be construed as “blaming society” for the problem or that the solution consists of “building youth centers”.
  • Work with Batts to actually fight crime; defer to his expertise at every opportunity.
  • Provide high-minded leadership on protecting civil liberties; on this defer to nobody. However, limit riot-bait to national and global issues. For example, city proclamations calling for bringing George W. Bush to justice and the like will only cause rioting on right-wing talk radio, leaving Oakland neighborhoods and businesses unscathed.

Next, finances. Similarly no-brainer suggestions:

  • Repeat early, loudly, and clearly that Oakland has an unsustainable spending problem, and everyone, especially your loyal allies in and funded by city government, are going to feel immediate pain.
  • Immediately push through cuts, primarily to areas you favor politically, sparing police and maintenance as much as possible.
  • Immediately push through revenue increases, e.g., tackle mis- and under-priced parking.

Beyond the above mandatory issues, a few less pressing but visionary actions for you to consider adding to your mayoral legacy:

  • Do everything you can to signal (and perhaps do a little of substance too) that you believe Oakland is the eco-city of the future, urban permaculture doers are heroes, and Oakland should be the world leader in marijuana business and education. Each of these increases Oakland’s specialness, and eliminates any future challenge from Kaplan. (If you’re moderately successful on the two major issues above, you also eliminate any traction Tauman or Russo might otherwise gain during your first term.)
  • Make Oakland the leader in “open” policy. There are obvious opportunities around city data, software procurement, and open licensing of city publications. The last would even help improve the article about you on Wikipedia. ☺ I and many other technology professionals and advocates of openness who live in Oakland would love to help. Some of us work for Creative Commons and other organizations with deep expertise in this area.
  • In another decade, autonomous vehicles will reshape cities. Establish some kind of an unpaid citizens committee to investigate how Oakland can prepare.

Here’s to great outcomes for Oakland, and your incredible success as mayor!

Mike Linksvayer
Golden Gate District, Oakland

Your public domain day

Saturday, January 1st, 2011

January 1 is public domain day, where in many parts of the world, some old works become free of copyright restrictions. In the U.S. no works will become so free due to the passing of time until 2019 — assuming the duration of copyright restriction is not again retroactively extended before then.

Fortunately you can add your contemporary works to the public domain right now, using the CC0 Public Domain Dedication. I try to put all of my “creations” into the public domain. See the footer of this post’s original location for a deployment example.

For software, using the Unlicense may be more familiar: copy the unlicense text into a file called COPYING, LICENSE, or UNLICENSE in your source tree — see the site.

One nice thing about well-crafted public domain dedications is that there ought be no interoperability problems among them, so there can be innovation (branding, legal language, community, supporting infrastructure) that would be harmful among more restrictive instruments. That’s not to say public domain instrument proliferation ought be encouraged willy-nilly — the instruments have to be well-crafted and users shouldn’t have to evaluate an infinite variety of them.

None of this is to deny that every single day ought see massive growth of the public domain — it should be the default — nor that copyleft licenses are useful tools for getting there in the long term and mitigating some damage in the short term. Eventually I will speculate on the tradeoffs between using public domain dedications and copyleft licenses for contemporary works, but for now, today is public domain day!

This post is an expansion of two conversations on identi.ca.

Addendum: I further recommend Lucas Gonze’s recent post Why I put my work into the public domain.

Another: See Arto Bendiken’s The Unlicense: The First Year in Review.

Federated Social Web Status[Net]

Friday, December 31st, 2010

Evan Prodromou just published his Federated Social Web top 10 stories of 2010. It’s a great list, go read — readers who aren’t already familiar with Prodromou, StatusNet, identi.ca, OStatus, etc. probably will have missed many of the stories — and they’re extremely important for the long-term future of the web, even if there are presently far too few zeros following the currency symbol to make them near-term major news (just like early days of the web, email, and the internet).

I suggest the following additions.

Censorship of dominant non-federated social web sites (e.g., Facebook, Twitter, YouTube) occurred around the world. While totally reprehensible, and surely one of the top social web stories of 2010 by itself, one of its effects makes it a top story for the federated social web — decentralization is one of the ways of “routing around” censorship. I’d love to have mountains more evidence, but perhaps this is happening.

Perhaps Evan did not want to self-promote in his top 10, but I consider the status of his company, its services, the software they run (all called ), and the community around all three, to be extremely important data points on the status of the federated social web, and thus inherently top stories for 2010 (and they will be again in 2011, even if they completely fail, which would be a sad top story).

I hope that Evan/StatusNet post their own 2010 summary, or the community develops one on the StatusNet wiki, but very briefly: The company obtained another round of funding and from the perspective of an outsider, appears to be progressing nicely on enterprise and premium hosting products. The StatusNet cloud hosts thousands of (premium and gratis) instances, and savvy people are self-hosting, mirroring the well-established wordpress.com/WordPress pattern. The core StatusNet software made great strides (I believe seven 0.9.x releases), obtained an add-ons directory, and early support for non-microblogging features, e.g., social bookmarking and generic social networking (latter Evan did mention as a non-top-10 story; of course any such features are federated “for free”). By the way, see my post Control Yourself, Follow Evan for the beginning story, way back in 2008.

2010 also saw what I consider disappointments in the federated social web space, each of which I have high hopes will be corrected in the next year — perhaps I’ll even do something to help:

StatusNet lacks full data portability and account migration.

Nobody has yet taken up the mantle of building a federated replacement for Flickr.

Unclear federated social web spam defenses are good enough.

Nobody is doing anything interesting with reputation on the federated social web — no, make that, on the social web. This is a major befuddlement I’ve had since (2002), at least. had an excuse as the first “social network”, (1999) innovated, then nothing. Nothing!

Far too few people are aware of the challenges and opportunities of maintaining and expanding software freedom/user autonomy in the age of networked services, a general problem of which the federated social web is an important case.

Finally, a couple not-yet-stories for the federated social web.

Facebook and Twitter (especially Facebook) seem to have consolidated their dominant positions in nearly every part of the world, having surpassed regional leads of the likes of Orkut (Brazil and India), Bebo (UK), MySpace (US), Friendster (Southeast Asia), etc. and would-be competitors such as shut down (e.g., Jaiku and Plurk) or considered disappointing (e.g., Google Buzz). However, it seems there are plenty of relatively new regionally-focused services, some of which may already be huge but under the radar of English-speaking observers. An example is , Sina.com’s microblogging service, which I would not have heard of in 2010 had I not seen it in use at Sharism Forum in Shanghai. It’s possible that some of these are advantaged by censorship of global services — see above — and cooperation with local censors. Opportunity? Probably only long-term or opportunistic.

Despite their high cultural relevance and somewhat ambiguous status, I don’t know of many © disputes around tweets, or short messages generally. Part of the reason must be that Twitter and Facebook are primarily silos, and use within those silos is agreed to via their terms of service. I’m very happy that StatusNet has from the beginning take precaution against copyright interfering with the federated case — notices on StatusNet platforms are released under the permissive Creative Commons Attribution license (all uses permitted in advance, requiring only credit), which clarifies things to the extent copyright restricts, and doesn’t interfere to the extent it doesn’t. (Also note that copyright is a major challenge for the social web in general, even its silos — see YouTube, which ought be considered part of the social web.)

All the best to Evan Prodromou and other federated social web doers in 2011!

As demonstrated above, I cannot write a short blog post, which puts a crimp on my blogging. Follow me on StatusNet’s identi.ca service for lots of short updates.

Retaining the right to censor is an act of hate

Tuesday, December 14th, 2010

Nina Paley (I highly recommend all her animations and appreciate her free culture activism) has an idea called the copyheart:

Use it wherever you would use the ©copyright symbol. Instead of

© Copyright 2010 by Author/Artist. All Rights Reserved.

you could write

♡2010 by Author/Artist. Copying is an act of love. Please copy.

I love the sentiment. Mike Masnick thinks the copyheart is cool. Unsurprising, since he doesn’t appreciate public copyright tools. That’s a problem, since cool without the aid of rigorous public copyright tools fails to build a commons that everyone can use. We don’t need help with materials that can be used by those with a low level of legal exposure: that’s everything that isn’t held in secret.

Expanding on the problem: unfortunately one automatically obtains copyright the moment one produces an original expression in a fixed form (e.g., this blog post). Copyright is a poor name, for it isn’t the right to copy; rather it is the exclusive right to restrict others from making copies (including altered copies, performances, and an ever-growing list of nearby uses, essentially forever). Copyrestriction would be better. However, others aren’t restricted automagically (and when attempts are made to do so, restrictions are usually massively over-applied); the copyright holder must take action, must play the role of the censor. Censorright would be even more apt. Not granting rights to the public in advance means one is retaining the right to censor.

Why would Paley want something that grants the public no rights in advance, while complaining loudly about some Creative Commons licenses for not granting enough rights in advance? Probably because she’s skeptical of public licenses, period, claiming they legitimize copyright. I almost completely disagree: copyright exists, is automatic, and is ever-increasing in scope and restrictiveness; public copyright tools are just a reality-based response that allow opting out of some or all of one’s right to censor, can offer limited protection (in the case of copyleft) from downstream censors, and also signal that some or all of a censor’s right is not desired, and most importantly help build substantial projects and bodies of work that do not rely on censorship (eventually evidence has to matter).

Now Paley is well aware of these arguments, and addresses some of them in the Copyheart Manifesto (which is more like a FAQ) and elsewhere. She says that free licenses “aren’t solving the problems of copyright restrictions.” That’s something that needs debate. I’d argue they’re one of the few rays of light against censorship, and they are creating space for “solutions” to be developed (see “most importantly” previous paragraph). She even almost directly addresses the problem that copyheart-like mechanisms (Kopimi is very similar; “all rights reversed” is more opaque simple statement that has been used occasionally for decades that Paley notes):

Q.Is the ♡Copyheart legally binding?

A. Probably not, although you could test it:

Mark your work with the ♡Copyheart message.
Sue someone for copying it.
See what the judge says.

We really don’t think laws and “imaginary property” have any place in peoples’ love or cultural relations. Creating more legally binding licenses and contracts just perpetuates the problem of law – a.k.a. state force – intruding where it doesn’t belong. That ♡copyheart isn’t a legally binding license is not a bug – it’s a feature!

Sadly, when the right to censor is the automatic default, it is not using a legally binding license that perpetuates the problem, but I repeat myself. I appreciate offering the test above, but it is far too easy a test (though I don’t know how it would turn out). Takedown notices, other chilling effects, and just plain avoidance, are far more common than actual suits. A better test would be this:

  1. Mark your work with the ♡Copyheart message.
  2. Have someone else upload the work to Wikimedia Commons, not mentioning that you asked them to.
  3. See if the Wikimedia Commons community is willing to rely on your copyheart message to make and keep available your work.

One reason the work probably won’t remain on Wikimedia Commons (note I’d be very happy to be proved wrong) is that copyheart doesn’t clearly say that altering the copyhearted work is ok with the copyhearter. Permitting adaptation is a requirement for free culture; Paley agrees.

The situation may not be totally hopeless for copyheart. Kopimi started as an equally simple exhortation to copy. There are some works on Wikimedia Commons labeled as Kopimi (though I’m not sure how many if any are only relying on Kopimi; many works on Wikimedia Commons are multi-licensed), though the template used for Kopimi uploads on Wikimedia Commons goes beyond simple exhortation to copy:

This work is labeled as Kopimi, meaning that the copyright holder of this work does not only release it, but specifically requests that this work be used and copied for any purpose, including unlimited commercial use and redistribution. It is believed in good faith that a work classified as Kopimi is free to use in any way, including modification and the creation of derivative works.

Now it would be possible to take copyheart in this direction, say:

♡2010 by Author/Artist. Copying and adaptation are acts of love. Please copy and adapt for any purposes.

One may as well finish the job and back this sentiment with a rigorous legal tool that takes every step possible to rid oneself of the right to censor, worldwide:

♡2010 by Author/Artist. Copying and adaptation are acts of love. Please copy and adapt for any purposes without any restrictions whatsoever.

The link is to the backing legally rigorous tool, CC0.

Speaking of censorship, the EFF has been doing a fantastic job in fighting many of its forms. Please join them in saying no to censorship.

Not only does EFF fight censorship, they also retain almost no right to censor works they produce. They use a Creative Commons Attribution license, which only requires giving credit to make any use (well, any use that doesn’t imply endorsement). You should also join them is saying no to censorship in this way — no to your own ability to be a censor.

You should also make annual donations of $ to both CC and EFF, and send ♡.

Collaborative-Futures.org

Thursday, August 26th, 2010

The 2nd edition of Collaborative Futures is now available, and the book has its own site and mailing list–there will be future editions, and you can help write them.

I did a series of posts (also see one on the Creative Commons blog) on the book sprint that produced the 1st edition. The 1st edition a highly successful experiment, but unpolished. The 2nd edition benefited from contributions by all of the 1st edition’s main collaborators, successfully incorporated new collaborators, and is far more polished. Also see I think the whole team is justifiably proud of the result. Please check it out and subject to harsh criticism, help with the next edition, or both.

You can also republish verbatim, translated, format-shifted, or modified versions, or incorporate into your own materials (e.g., for a class)–the book and all related assets are released under the Creative Commons Attribution-ShareAlike license — the same as Wikipedia. I don’t think we took advantage of this by incorporating any content from Wikipedia, but as I’m writing this it occurs to me that it would be fairly simple to create a supplement for the book mostly or even entirely consisting of a collection of relevant Wikipedia articles — see examples of such books created using PediaPress; another approach would be to add a feature to Booki (the software used to create Collaborative Futures) to facilitate importing chapters from Wikipedia.

Here’s a copy of my testimonial currently on the Booki site:

I was involved in the Collaborative Futures book sprint, the first book written using Booki, and the first FLOSS Manuals project that isn’t software documentation. I was amazed by the results materially and socially, and even more so by the just completed 2nd edition of Collaborative Futures, which successfully incorporated several new contributors and benefited from new Booki features.

I am inspired by the potential for book sprints and the Booki software to expand the scope of collaborative production in a wide variety of contexts, especially education. Booki is an exciting new innovative platform that is bringing book production online and is an important new form of free culture / free knowledge production. Platforms that expand the categories of works that can be radically improved through free collaboration (beyond software and encyclopedias) are absolutely essential to building a good future. I enthusiastically endorse Booki and encourage all to use and support it.