Economics

Occupy 980

Wednesday, December 7th, 2011

I’m in agreement with Timothy B. Lee’s posts a month ago that urban freeways are not needed and harmful, but whether any particular urban freeway ought be actively taken down depends. (Of course no more ought be built and nearly all existing ought not to have been built.)

Lee’s posts got me thinking about which of Oakland’s freeways ought be torn down first.

The map above gives a pretty good idea of Oakland freeways. Clockwise from the top there’s 80/580 going north into Berkeley, 24 into a tunnel through the hills, 580 and 880 continuing on for a long way to the southeast and into San Leandro (there’s also 13 in the hills connecting 24 and 580, the only segment completely off-map), and 80 across the bay to San Francisco. Then there’s 980 connecting 24 and 880. 980 is the obvious segment to go:

  • Traffic volumes on 980 are less than any of the others (excepting 13).
  • 980 cuts West Oakland off from downtown, and causes the former to be completely encircled by freeways.
  • Despite being relatively low traffic, the real estate used by 980 is a city block wide. About 29 core city blocks could be freed for other uses.
  • 980′s primary purpose is apparently for providing access to downtown Oakland. A freeway through downtown is not needed for downtown access. Drivers wanting downtown access need to drive on downtown streets, and can do so just a tiny bit sooner. Downtown Oakland streets have lots of capacity and are rarely congested.
  • In the next decades, autonomous vehicles will push “not needed” to the extreme, as such will enable much, much higher capacity on the same roads. Oakland, like all cities, ought to be planning for autonomous vehicles now.

Before last month, I had not realized that 980 was not completed until 1985, which by itself does not strongly support my understanding of the local narrative (which I must have heard by 1995) concerning the extent to which 980 negatively impacted West Oakland. But apparently construction started in 1964. Planning was underway in the 1950s. I’m don’t know when about 29 blocks were destroyed to make way for 980 (I’d appreciate pointers), but it could have been 20 or more years before completion, and even if not, the knowledge that they would be destroyed must have contributed to isolation.

Perhaps Occupy Oakland ought move to some of the greenery along 980, or Grove-Shafter Park, which is more or less under the interchange where 24, 580, and 980 meet — more than symbolic, a physical barrier separating the poor from the powers that be. They wouldn’t need to make any specific demands about what would come after destroying the segment of the system that is 980. 29 blocks of vertical hemp farms? Mixed income housing? Art studios? “Occupy Park”, a grand urban park named for the movement? Skyscrapers? Ironically nostalgic monorail line? No need to decide now, dream on!

Mozilla Public License 2.0 and increasing public copyright license compatibility

Tuesday, December 6th, 2011

Incompatibility among public copyright licenses dampens their potential for reducing underlying friction caused by copyright. Increasing compatibility among public copyright licenses is one of the successes of the free/libre/open source community, or so I think. Without long-term, distributed collaboration among license stewards and projects released under public licenses, it would have been easy to obtain a world in which it usually isn’t legally possible to use code from one project in another. (A shared understanding of what constitutes “free” and “open” really helps — the scope for incompatible-in-spirit licenses is greatly reduced, and distributed collaboration facilitated by everyone sharing broad premises.)

I’ve been watching from afar development of the Mozilla Public License version 2 (going for nearly 2 years, I believe about the right amount of time to version a widely used public license) almost exclusively because I was eager to see it become GPL compatible, and how it would achieve this.

Luis Villa explained most of the “how” three months ago. To make sure I understand, here’s my summary:

  • MPL 1.1 is not GPL-compatible. MPL 2.0 will be, but with a few caveats to ensure that projects released under the MPL won’t become GPL-compatible unintentionally, and that there’s a way for new projects under MPL 2.0 that really, really don’t want to be GPL compatible, don’t have to be.
  • Code from a project is released under MPL 2.0 (and not multi-licensed), it can only be made available under the GPL* when incorporated into a larger project that is already GPL licensed, i.e., there has to be a good reason.
  • The entity doing such incorporation in the point above has to offer the MPL code under the MPL and additionally the GPL. A downstream entity can choose to only use the GPL. In other words, people who want to use the original project’s code line under the MPL have ample opportunity to do so, until it is truly forked into a GPL-only version.
  • MPL 1.1 projects (1.1 has a “future versions” clause) modified and released under MPL 2.0 are not GPL-compatible in the manner above unless the project was already multi-licensed under the MPL and GPL (the most important MPL 1.1 licensed projects are multi-licensed), i.e., the intent to allow for use under the GPL is already established.
  • Projects that want to use MPL 2.0 and really don’t want to be GPL compatible can include an “Incompatible With Secondary Licenses” notice.

I think the last point is an unfortunate complication (such projects could stick with MPL 1.1, for instance), but I trust that there are good stakeholder use cases for it. But that’s a minor nit. Villa and other people who worked on MPL 2.0 did a great job and get congratulations and thanks from me.

One of my dreams for Creative Commons Attribution-ShareAlike 4.0 is that it be one-way GPL compatible, as MPL 2.0 will be. MPL 2.0 demonstrates mechanisms for achieving GPL compatibility without upsetting current licensor expectations, which ought be a useful perspective from which to evaluate options for CC BY-SA 4.0. Though CC licenses should not be used for code, it’s easy to see a future in which most “culture” includes “code” and it is an unnecessary pain to keep their licenses separate in all cases. Also, there is some demand for a source-requiring copyleft license for non-software works (BY-SA does not require adaptations to provide source, which is often OK for cultural works, but not always) and it doesn’t make sense to create another source-requiring copyleft license in addition to the GPL.

*Actually LGPL 2.1 or greater, GPL 2.0 or greater, or AGPL 3.0 or greater. MPL has a weaker copyleft than any of the GPL-family licenses — MPL’s copyleft is scoped by file, LGPL’s by library, GPL’s by any linked code, AGPL adds requirement for source distribution to network services.

Addendum 20120103: MPL 2.0 is released today. FSF has added MPL 2.0 to their free licenses page with a GPL compatibility explanation.

No more child veterans

Saturday, November 12th, 2011

Yesterday was Veteran’s Day. In support of that, I donated to the Coalition to Stop the Use of Child Soldiers.

In the U.S. (as in most jurisdictions), people have an odd attitude toward military veterans. Even those who generally condemn the activities and costs of the (especially U.S.) military as stupid and counterproductive, or much worse, fall into the grip of nationalist religion and “honor” people who directly participated in mass murder. Those who generally support the activities and costs of nationalist armies go out of their way to signal how much they honor and support mass murderers. But, apart for the most compassionate of the former, most zealous of the latter, and some veterans and their lobbyists, generally military veterans are kicked the the curb — thanks for murdering for the nation-state; good luck on the streets and in our fine institutions!

Fortunately, there is a way out of this hero/murderer/reject paradox (other than ceasing U.S. military interventions; yes I want that, but I’m not that ambitious today) — recognize that most U.S. soldiers are children. As such, they should be pitied and rehabilitated. Furthermore, the minimum age for joining the U.S. military ought be raised to at least 21, and a 4 year college degree required (up from 17 and high school, with caveats). Never again should a child be forced to choose between murder and no money for college.

Commons experts to develop version 4.0 of the CC licenses

Thursday, November 3rd, 2011

As described on the Creative Commons blog some initial discussions were had at the CC Global Summit about 6 weeks ago in Warsaw. I’m looking forward to the start of in depth discovery, analysis, and debate of pertinent issues on the cc-licenses list, the CC wiki, and elsewhere over the coming months. Please join in, commons experts.☺

I gave a brief presentation on one of those issues at the summit, on the “NonCommercial” term of some CC licenses (odp, pdf, slideshare). [Addendum 20111104: This talk was not recorded. Only slides are available. Don't watch the videos below if you're only looking for a talk on NC!]

More relevantly (to 4.0; yes, NC is pretty relevant, becoming less so, the commons is super relevant, indeed all important) though more abstractly, I also organized a session on “CC’s role in the global commons movement”. I’m very happy with how that turned out, but it is only a tentative beginning, about which I will write further. For now you can read Silke Helfrich’s summary post and slides, Tyng-Ruey Chuang’s presentation text, Leonhard Dobusch’s slides, and Kat Walsh’s presentation text and download or watch at archive.org or YouTube:

Because I may never get around to blogging it separately, I also gave a presentation on “what’s happened in Creative Commons and the open community over the last 3 years.” You may recognize one slide from an earlier post. View slides (odp, pdf, slideshare) or video at archive.org or YouTube:

Open World Forum: Knowledge Commons Fail/Fix

Thursday, October 13th, 2011

A few weeks ago I gave a talk at Open World Forum. Slides (odp, pdf, slideshare), video (archive.org, YouTube):

I rushed through my final slides and promised to expand on them virtually, which I’ve done here with more slides (odp, pdf, slideshare), or watch a video narration of same (archive.org, YouTube):

Thanks to Open World Forum co-president Louis Montagne and Knowledge Commons track leader Florence Devouard for inviting me to participate!

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.

DATABASE at Postmasters, March 2009
Gulliver and the Liliputans, trade card for J. & P. Coats spool cotton, late 19th c by Donaldson Brothers, Five Points, N.Y. / Public Domain.

Cryptocurrency race to the bottom?

Monday, May 30th, 2011

I don’t know a whole lot about , but from what I’ve heard (a) governments, unable to fight math, will soon crumble, or (b) Bitcoin is nothing more than a scam meant to enrich its inventor and early adopters and increase the gap between haves and have-nots, or (c) both.

I’d guess none of the above. If Bitcoin speculation, increased acceptance of Bitcoin for real goods, or both continue apace such that the Bitcoin phenom grows for a long period of time (all questionable), I predict that governments and any other entity with a large measure of control over how it can demand payment will launch their own cryptocurrencies, seeking endowments for themselves much as Bitcoin’s inventor and early adopters may have gained.

First a quick aside on the welfare and distributional effects of an endowment for cryptocurrency initiators, and Bitcoin’s in particular. It doesn’t matter all that much, at least :* with zero transaction costs (perhaps cryptocurrencies will get us closer to that ideal) resources will be put to their most efficient uses, regardless of initial distribution. Of course reality will diverge from perfect theory, but given gross inefficiencies that exist in the world today, it’s hard to say that whatever change could be engendered by Bitcoin taking off would certainly be worse. Regarding distributional effects (i.e., equality), it’s hard to see how at least in the short term potentially massive wealth for the Bitcoin inventor and early adopters changes much. It is doubtful these people are among the pre-Bitcoin megarich. Scam or not, I don’t see how Bitcoin distribution increases or decreases inequality significantly unless one expects Bitcoin to become the only currency in the world. I consider this highly unlikely.

Because, repeating close of first paragraph: once Bitcoin is considered as tested and important, any entity that can would be crazy to not seek a windfall for itself by initiating a new cryptocurrency with rules such that it can gain a significant fraction of the wealth embodied in the currency for itself, as the Bitcoin developer and early adopters supposedly have. A significantly powerful entity (i.e., a government) would be significantly tempted to initiate new cryptocurrencies regularly, just as the temptation holds to inflate traditional fiat currencies now. These entities, and many others besides, will also want to experiment with cryptocurrency rules (e.g., Bitcoin’s decreasing minting to a set limit, constant growth, other?).

I have no idea how any of this will play out. On one hand, what are the competitive pressures that will drive cryptocurrency evolution? Is it conceivable that network effects could result in only one cryptocurrency holding value, perhaps Bitcoin? On the other hand, if cryptocurrencies become economically important, they will surely have deep and far reaching effects, even if those don’t include the sudden collapse of governments and the rise of a Bitcoin oligarchy. It seems well worth thinking ahead about these effects from a variety of perspectives: one example.

Also recommended: Bitcoin, what took ye so long? on strands of thought preceding Bitcoin, by Nick Szabo. Indeed, go read everything Szabo has written.

I understand that emotions run high concerning Bitcoin. “Race to the bottom” in the title of this post is merely intended to provoke. The phrase is often abused. Feel free to disabuse me of any incorrect thoughts.

Oh, and feel free to send ฿ to 153ofsZ1PrnCnDGjvWAenRJc53TRhR9BzK.☻

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.

NYT digital subscription plans as Kickstarter project backer levels

Saturday, March 19th, 2011

Apart from curiosity about what the New York Times forecasts for the project and how they arrived at same, I really don’t care one way or the other about the upcoming New York Times paywall.

However, the paywall’s convoluted pricing cries out for taking the form of Kickstarter project backer levels. I haven’t done justice to the NYT plan and have done injustice to well-crafted Kickstarter project backer levels I recently admired. Apologies to all.

NYT Paywall as Kickstarter Levels

Addendum 2011-03-22: Thanks to Kickstarter for appreciating and blogging about this post. I didn’t mean to suggest “the whole thing would work best as a Kickstarter project: funding goal + tiered reward options + the assurance that you will only be charged if they do indeed survive the death of print/revolt of the internet” but that’s certainly correct! For some of the reasons why, extrapolate from Timothy B. Lee’s two recent posts on the paywall, Shoe-Leather Reporting at the New York Times and Misguided Moralism in the Paywall Debate. For a future with good journalism, Kickstarter is of far more relevance than any paywall.

Why a punch in the face* is the appropriate response to use of the phrase “business model”

Saturday, January 8th, 2011
fist
Seiken by Kurmis / CC BY

The utterer of “business model” has attempted to raise their status with a superfluous word and has only confused whatever the issue at hand. The utterer is probably among the confused. The listener obtains only entropy and lower relative status. A punch serves to equalize the situation.

In inappropriate conveyance of status, “business model” bears likeness to beginning a statement with “So, ”:

Starting a sentence with “so” uses the whiff of logic to relay authority.

Ugly stuff.

Vivek Wadhwa, my favorite TechCrunch writer, seeks to educate the confused (strikethrough added):

Developing the right product is hard. But what is harder is building a good business model.

However, this and other uses throughout the article only demonstrate the superfluousness of “model”.


*metaphorically
with scare quotes, or snarky tone, is ok; beware of inadvertent homage