paper ideas


5
Aug 10

Notes on Eugene Bestor’s ‘Backwoods Utopias’

A few months ago I finished reading Eugene Bestor‘s ‘Backwoods Utopias‘, a book on the Utopian social-communitarian movements of the pre-Civil War US. Some belated notes on the book’s themes follow.

The average high school US history textbook gives a thumbnail sketch of these movements, but for those who didn’t get that or don’t remember it, the gist is that, from very shortly after Europeans reached North America until right around the Civil War, groups of people regularly launched themselves into the North American wilderness, trying to found new communities organized around communitarian and egalitarian principles. They met with some success, but eventually the movements petered out, with none of them truly surviving into the modern age.

Owen by BinaryApe, used under CC-BY

The tie from this book to my own interests should be clear, but if not, I should make them explicit: free and open source software often thinks of itself as being sui generis, but in fact it is part of a history (in this country) of retreat from established economic structures with the intent of creating parallel systems that would eventually compete with or replace those established structures with something simultaneously individually empowering and socially just. (See also.) I’m both personally and professionally curious about gleaning lessons from such past experiments- so I picked up the book. If any of this blog’s readers have suggestions either of more histories of this movement, or of histories of other similar movements (watch this space for a post on the local food movement soon), please do let me know in email or comments.

Unfortunately, Bestor’s intended follow-up book (covering the 1840s to the end of the movement) was never completed, which limits the lessons that can be drawn about the decline of the movement.  Nevertheless, some observations and themes from the book:

  • The movement had a broad spectrum of motivations and philosophies- some were heavily religious, while others were overtly anti-religious; some had (or were intended to have) quite complex governance systems, while others were nearly anarchist, and indeed Marx condemned them in strong terms because (to over-simplify) they were not dedicated to fighting the good fight in the cities. Interestingly, while the community focus of these groups was typically very strong, in modern terms we might also call them libertarian (or what Erik Olin Wright calls ‘interstitial’ revolutionaries): they all believed that they had the right and the ability to make a better world by striking off on their own, rather than working within or against established structures.
  • Religion was initially a major motivating force; this faded over time, but Bestor does not make it clear why later groups tended to be non-religious. Interestingly, American critics of later movements like Owenism apparently tended to focus on this non-religious aspect, rather than the practical/anti-capitalist issues modern critics might focus on.
  • As with every movement, looking at who left is often as important as understanding who stayed. In particular, Bestor mentions that when pragmatists became frustrated and left New Harmony (perhaps the highest profile of the various communities), those left behind were a combination of those too lazy to leave and those too fanatic to leave. This was a huge problem for the morale of the remaining pragmatists, who resented the free-riders and were driven nuts by the fanatics, and so they repeated the cycle.
  • Relatedly, Bestor argues that the repeated talk of ‘everyone will live in our miraculous new society any day now’ meant that many newcomers were not prepared for the long haul; that may have disillusioned some people and contributed to a sense of lack of momentum. To paraphrase Bestor, ‘a new society cannot be built on excuses.’
  • When the movement started, it was actually pretty easy to get a community going- lots of land was effectively empty, and the median community size in the US was in the low hundreds, making it quite easy to form a community that had all the ‘comforts’ (such as they were) of traditionally organized communities. As time progressed, two things began to work against this: first, more and more ‘normal’ landowners migrated to the midwest, causing land to become more scarce, and second, even the smallest villages became larger as the country’s overall population grew. This meant that finding enough space for a ‘basic’ community became a much more capital intensive process over time. Not coincidentally, later communities tended to have wealthy patrons- with all the plusses and minuses that brings.
  • As economic complexity increased (more machinery, more specialists) it became harder to create a self-sustaining village, especially if your human capital stocks were limited to ‘believers.’ For example, when the movement started in the late 1600s/early 1700s, having a self-sustaining community required very little specialization, while by the mid-1800s, it was understood that you needed machinists and manufacturers who would trade with other areas. Bestor says that New Harmony was bitten by this, as the land they bought for the town had the hardware for extensive wool manufacture, but lacked the people familiar with the machines, killing an expected source of financial sustainability.
  • Over time, some of the social goals of early communitarians became more broadly accepted or supplied by other organizations. For example, public education was a significant goal of New Harmony, but over the course of the 1800s, that became more common in non-utopian communities. New Harmony also had a concept of mandatory social insurance; unions started providing similar services in the late 1800s. This again made recruitment harder.
  • As for most world-changers, the gap between theory and practice was often large. Robert Owen, the wealthy patron of New Harmony, created an elaborate philosophical scheme intended to encompass everything from the individual to the nation-state, but he was bad at creating practical schemes, which led to constant reorganizations at New Harmony. This may reflect the extreme difficulty of organizing a full society; capitalism has the advantage of being simple and direct in general scheme relative to a centrally planned society like Owen’s.

I’ll refrain from drawing any direct conclusions for free and open source software here, in part because many of them will be obvious to many of my readers, and also because my reading of the book (especially several months after the fact) is inevitably heavily biased by my own thinking about social movements like this one, so I’m not sure whether any ‘lessons’ would reflect actual history or just my interpretation (compounded with Bestor’s.) With or without direct applicability, though, the book was an interesting read for a history nut, and left me with a lot of food for thought.


19
Apr 09

all the cool kids are writing about the google book search settlement

Samuelson

Picker

Grimmelman

Perhaps some day before the case settles I’ll actually be able to read them all. In the meantime linking here so that I can find them all later.


22
Sep 08

computer usage data bleg (update: and server market share)

Hey, all. I’m in need of data about ‘typical’ computer usage- i.e., ‘in 2007, the average computer user spent X% of time on the internet, Y% of time doing word processing, Z% of time listening to music, etc.’ The ideal data set would have this information for a number of years- ideally going back at least to 2000 A.D. (aka ’1 B.iTunes.’) I’ve been googling for a bit and have had no luck. If anyone can point me at such data, I’d be extremely appreciative. Thanks!

Relatedly: (added later): similar long-term numbers for server market share, both by OS and by chip family (x86 v. everyone else, primarily) would be terrific to have if anyone knows of a source of them (ideally without paying Gartner bazillions, though I really need to look into whether or not the school’s Bloomberg subscription gives me access to that.)


10
May 08

interesting research on ‘conditional cooperation’

Interspecies cooperation

Interspecies cooperation by Barry Rogge. License:

For those interested in some of my previous writings on intrinsic motivation, this survey paper by Simon Gächter may be of interest.

Key sentence:

[W]e find strong evidence that many people’s attitude toward voluntary cooperation is conditional on other people’s cooperation… Moreover, the fact that many people contribute more the more others contribute also speaks against pure altruism explanations, because they predict that people reduce their own contributions when informed that others already contribute to the public good.

Basically, the paper argues (and justifies through a survey of experimental evidence) that a majority of people are ‘conditional cooperators’ who cooperate in community projects (voting, paying taxes, charity work, etc.) if and only if other people cooperate. If they think others are ‘defecting’ (i.e., not cooperating) then they will stop cooperating as well.

The paper also has some more detailed observations that come out of the experimental work; among them that voluntary cooperation is fragile; group composition matters (i.e., groups with more conditional cooperators will be healthier); and that ‘belief management’ maters- i.e., if people think that they are in a group with more conditional cooperators, that group will be more robust. None of these will come as a huge surprise to anyone who has been involved with volunteer communities, but still interesting to see it experimentally confirmed.

I’ve always suspected that something like this is the case, and that it explains in part why the GPL is so successful, since it uses copyright to force cooperation and penalize defection, and (importantly) makes a clear public statement that that is the case, which serves a signaling function (everyone in the community knows these are the ground rules) and a filtering function (people who aren’t interested in collaborating don’t join as much as they join other groups.)

The paper is only 25 pages and fairly readable; if you’re interested in the dynamics of volunteerism I recommend it.

Those of you who aren’t into economists and their fancy ‘measurements’ may also want to look at this related early paper, which is somewhat dated (the concept of low and high authoritarians is sort of discredited at this point) but still possibly of interest in explaining some of the psychological mechanisms at work here.

(Came to this by way of this paper on tax evasion, which looks to have many other interesting citations that I should investigate once exams are done. Only Telecoms left…)


24
Jan 08

morning link bits


14
Jan 08

wesabe ‘data bill of rights’

Wesabe’s Marc Hedlund is speaking at the Princeton Cloud Computing seminar I’m at. Their ‘data bill of rights’:

This Data Bill of Rights is our promise to you.

  • You can export and/or delete your data from Wesabe whenever you want.
  • Your data is your data, not ours. Our job is to help you understand and act on your data.
  • We’ll keep all of your data online and accessible for as long as you have an account. No “archive access” charges.
  • Any data you want us to keep private, we will.
  • If a question comes up not covered by these rights, we will answer it remembering that your data belongs to you.

Interesting. My intuition is that this is a really good start in the right direction for web apps; he himself notes, though, that it isn’t legally binding. They are considering doing that- will be very interesting to see that if/when it happens.


6
Dec 07

Voting With Your Feet and Other Freedoms

This Post In A Nutshell (aka, the Murray Version)

No one should be surprised that social network users can’t ‘vote with their feet,’ because most users give up a portion of their autonomy when they choose to use web services. This post will suggest that protecting autonomy is desirable and should be designed in to software, and outline five qualities that such software would have.

[The rest of the post will not be brief; it is in part a draft of an essay for my class in 'Law in the Internet Society'.]

Continue reading →


2
Oct 07

hypothetical copyright exam question

mystery!

[picture: 'Unsolved Mystery', by ButterflySha, used under a CC-BY license.]

Hypothetical copyright exam question for your late-night pondering: If a poem is derived from statistical analysis of 22 books, but contains no actual direct sequences from those books longer than 2-3 words, is it a derivative work of those 22 books?

Thou shalt be I. . .
Thou shalt be I, and quench the
fire in a pit
dug in the

direction of this rock,
deliberately,
now thy peace, the green weed

and explain the high road from which
miraculously we had
been left unsolved.

from King of Eatable Birds, by Anne Mordeus and the machine.

[hypothetical, though I think probably less interesting, parallel patent exam question: if an evolutionary algorithm creates a better design than humans, and the humans can't necessarily explain why, is the resulting design or process still patentable?]

[Cross-posted from First Movers; comments over there.]


7
Aug 07

freedom ‘for users’- which users did you mean, exactly? (or, of users, user-deployers, and user-consumers)

“Free software… refers to four kinds of freedom, for the users of the software…”
–Free Software Definition, emphasis mine

“closing the [ASP] loophole would infringe on certain peoples rights and he [Moglen] didn’t see any way to preserve everyone’s rights…”
– Eben Moglen, as paraphrased here

[The rest of this post is not based on any conversations with FSF/SFLC folks on this issue, but merely on readings of essays/interviews/etc., and so their position here may represent a bit of a strawman. To the extent that the representation is inaccurate I apologize and will strive to fix it if someone points out the inaccuracies. That said, if it is a strawman, it is a useful strawman which helped me sort out my own thinking on the subject.]

who has the freedoms and the rights?

In one of my GPL posts, I mentioned that I thought that the question of ‘who holds the rights’ is a critical distinction between the ‘free’ and ‘open/pragmatic’ licensing camps. To the free camp, rights are held by users; and to the open/pragmatic camp, rights are held primarily by developers- who then grant most (but not necessarily all) rights to users. I thought I’d dig a bit more into that notion, particularly into the question of what a ‘user’ is in this day and age, because I think it helps explain the current dilemma around free software as deployed over the web.

who ‘users’ used to be

FSF has always insisted that “users” are the locus of all rights. In practice, to FSF, “users” has really meant “the people who install the software”- what I’ll call “user-deployers” or “deployers”, in comparison to “the people who use the software”- what I’ll call “user-consumers” or “consumers.”

In the beginning, this was not problematic- anyone who deployed free software also consumed it, so giving rights to all deployers also gave rights to all consumers.

As free software got more popular, this got a little more complicated- deployers were often systems administrators in an organization (who had full rights to modify the code) and the software was used by consumers in the same organization. These user-consumers were given the binaries but were not given enough permissions to install new versions of the binary, or access to source (though they could presumably obtain them for their personal, non-work PCs if they were skilled enough.) And so there was a gap between the rights of deployers (who could modify) and consumers (who could not)- a small gap, but a gap nonetheless.

In practice, this worked OK. The interests of user-deployers and user-consumers were not perfect aligned, but they were pretty close- deployers mostly wanted consumers to get things done and get out of the way, so they protected consumers to a large extent. In addition, even if they weren’t always exactly aligned, consumers and deployers were clearly both on the same side against the software vendors- both consumers and deployers wanted more freedoms than the vendors would necessarily have chosen to give. Given this combination, for most purposes it is fair to say that in practice user-consumers had the freedoms to use and modify- even if in practice those rights were granted to and proxied through the deployers hired by their organizations.

who ‘users’ are now

That brings us to the present day. With the advent of the LAMP-powered web, user-deployers and user-consumers of free software are often no longer in the same organization- the deployer, who was once the local sysadmin, is now the sysadmin of Google or Yahoo. As a result, the interests of the user-deployer and user-consumer are often poorly aligned or in outright conflict. In addition, the old tension between vendors and user-deployers, which helped protect user-consumers, has to a large extent vanished- since the deployer of the free software (the party that runs the compiled code) is now also the vendor.

In a web world, then, user-deployers have the same rights they’ve always had to use and modify. The FSF apparently believes that should not change. But since the deployers and consumers aren’t part of the same organization anymore, the deployers no longer protect the user-consumers, and so user-consumers end up frequently making use of free software without even the slightest ability to use and modify the software- and often even without the right to use and modify their own data!

This is, I think, part of why Matt Asay wants to call GPL ‘the new BSD‘- like the BSD, the GPL lets software vendors (in the BSD case, Apple; in the GPL case, Google) deliver software to consumers without also delivering the freedoms to use, modify, and redistribute. Some freedom is preserved- the freedom of the deployer to use and customize- but this is not, at least in my mind, the kind of freedom I’m aggressively interested in working towards.

so how to restore freedoms to user-consumers?

This problem isn’t easy to resolve systematically- since they are in conflict, any attempt to guarantee rights to user-consumers would seem to require some compromise of the rights of user-deployers. I admit I myself am a bit stymied on the issue, though I have some ideas.

Prof. Moglen and FSF’s position seems to be that the freedoms of user-deployers will trump those of user-consumers until someone comes up with a principled and rights-centric way to draw the line between the two. Unfortunately, Moglen seems skeptical this line can be drawn- and experience shows that he is usually right.

I remain interested in the problem, though, since in the end I’m much more interested in the freedoms of users than the freedoms of sysadmins. I hope that better understanding that there is more than one type of user takes me one step closer to figuring out where the line can and should be drawn.


26
Jul 07

thoughts from afar on OSCON

I’m obviously interested in what is going on at OSCON this year, since the overlap between web 2.0 and free/open software seems to be a major theme. Unfortunately, I couldn’t go, so I’m left lurking from afar.

John Eckman has some of the best notes I’ve found, at least on Eben’s talks- read his notes on Eben’s major speech and his notes on Eben’s chat/flamewar with Tim O’Reilly. It appears that in his introduction O’Reilly covered some of the same ground that I covered on Sunday, but it isn’t clear (at least from any notes I’ve been able to find) that Tim has answers to the questions he has posed.

Eben apparently said something to the effect of:

“talking about real freedoms … requires a discussion about public policy and long-term consequences of all this technology we’ve all put into the world”

I couldn’t agree more. We are standing at the brink of a huge change in how people store the data that makes up the emotional content of their lives. We must start coming to grips with the policy implications of that, just as government once struggled to come to grips with the impact of people storing the economic content of their lives in banks, and I’m excited to think that free and open services could be part of that. (We also need to think about other policy issues- patents, etc.- that can’t really be dealt with in isolation, but those aren’t my focus right now, even if they are Eben’s :)

That said, from John’s notes on Eben’s talk today:

The fundamental right with which Stallman has always begun is anyone’s right to run any program anywhere at any time for any reason – this has to include the right for people to run a program at any time *for anyone* – that is, provision of software as a service for other people. …

If the discussion about service provision is a rights conflict issue, it is critically important to frame that discussion in clear terms based on the rights perceived to be in conflict.

No rights based argument sufficient has been articulated which should compel the release of code which some people choose to run for third parties benefit. That doesn’t mean such an argument doesn’t exist…

I had already begun to try to formulate my argument in terms of rights, so I’m part way along this road already, but once you have such a broad interpretation of the rights of the user who execs the software, it becomes very difficult to convincingly articulate the rights of the user who puts data into the software, the value of the commons, and the rights of developers. I’m sure Eben is right that it will be worth the effort to try, but I’m not confident that I can succeed within that initial set of assumptions. Keep your eyes on this space, I suppose :)


This work by Luis Villa is licensed under a Creative Commons Attribution-ShareAlike 3.0 United States.