March, 2007


19
Mar 07

Notes from Prof. Eben Moglen’s talk on “The Empire & the iPhone: ‘Technology Platforms,’ the Commons, and the Way We Live Now”

Tonight I attended a talk by Eben Moglen titled “The Empire & the iPhone: ‘Technology Platforms,’ the Commons, and the Way We Live Now”, put on by the Information Law Institute Students Assocation at NYULS. They are hosting a Stallman talk on Wednesday; it is Krissa’s birthday so I won’t be attending that one.

The talk was a full hour, plus 30 minutes of Q&A. Necessarily, then, these notes are fragmentary (‘written’ on an N800). It is probably best to read them as jotted (and heavily paraphrased!) notes and highlights rather than expecting a coherent narrative. Don’t rely on these for reporting Eben’s thoughts- if you see something of interest here that you plan on quoting in a Serious Format, contact me, or better yet him, to confirm that it is acccurate.

I wish I had deep thoughts to add, but I’m pretty beat up tonight. Possibly more tomorrow. Nutshell version: I think Eben is obviously correct that platforms are loci of control, and hence are very dangerous for anyone concerned with rights in a digital context. (Not just software freedom, but freedom of speech, freedom from government eavesdropping, etc.) At the same time platforms (and the standardization they can create) can facilitate innovation at other levels in the stack, and efficiencies all over. Figuring out how to strike that balance may be as easy as just having good rules about platform licensing, but I have a gut feeling it will be more complex and difficult than that. At any rate, like I said, probably more of my own thoughts tomorrow.

The Talk

He wants to focus on non-license stuff, and instead focus on where we live now- the broader view of the environment rather than the specifics of one license. (ed.: of course the first question in q&a was about ms-novell. :)

The commons is here and not going away; production in 21st cent. will be community based, and traditional sellers are now realizing this, and reacting defensively or otherwise.

Rise of prosumer is critical; digital camera is the beginning of this but only the beginning; will impact much more than photography- stage shows, etc.

We now know that ownership of knowledge blocks, and/or makes inefficient, knowledge production. [ed.: he asserted in Q&A that we should issue patents under a formal adminstrative cost-benefit analysis scheme, but I'm not sure how one can even pretened to do that, given the sparseness of the economic research on the topic.]

Other than MS every single significant software vendor uses- depends on- output of commons. Not just culture and software but banking and money are now contested; paypal distributes banking. Ebay decentralizes vending.

Commons are now central both for the most and least powerful.

Many mechanisms for commons to protect itself; copyleft but also stubborn 12year olds and p2p. Needs all of them.

IBM and HP are doing well in large part b/c of harnessing commons.

Talked regularly to Bill Hilf, MS. Calculated that MS can bring 3.8 million manhours/week to the table; from sf.net + surveys done by rishab ghosh he gets (in 2004 ) 5 million manhours/week spent producing GPL software; now probably closer to 6m overall. So commons is the majority in some parts of software, even if not yet in other places in ip.

Despite the reality of production, commons is not the dominant theory of production. Proprietary mental models still dominant, which is why we still pay for phone calls. Skype is not perfect, but is still early and very threatening to a broad range of interests, and having an impact.

Question, then: owners will have their innings to respond; what will the response look like?

Says their answer will be the platform, which is (among other things) a safe box within which commons can be safely controlled/walled off.

The cell phone network is an example. It gives people impression that movement matters (“roaming”); that expensive hardware is necessary; that you must carry the state with you in the form of e911; that you must eventually give vast amounts of info to marketers.

Commons has better answers for all this (wifi, skype, etc.), but like MS, the cell people tie you to a platform and scare you w/ isolation if you leave the comfort and security of the platform.

The story Jobs spins is ‘There would be no music w/out the platform- people will stop singing w/out the platform.’ This is obviously ludicrous but we’ve bought into it. Despite his recent letter, Jobs is not really anti-drm; just doesn’t want to lose the platform.

“Who will make software if you sell it below cost?” is what the economists used to ask; now sony and xbox do this for hardware, and the economists justify it as a blade/handle model, which he finds economically implausible, unless we give them alternate forms of control so they can force the blades on us- this, again, is the ‘platform’.Says that Tivo’s GC finally checked in on gpl3; Moglen apologized for RMS’s use of “tivoization” as a phrase, but tivo still wanted the keysigning clause removed. Says Tivo even offerred removal of drm from the stored video, just as long as they could keep the subscription lockin by signing the software. If they gave away subs via hacking, they lose out. They want free software to compromise so that they can commit the “economic stupidity” of too-cheap hw.

Sees the near future as the process of maneuvering the commons through the obstacle course of platforms which benefit incumbents.

Notes that government is fertile grounds for creation of platform by fiat/incumbents.

Notes that not all platforms are the same; some more or less bad than others.

Job/wealth creation from the comon is not inherently bad, but it can create pathologies as people attempt to game or exploit the commons. He says we will need a language to describe this; we’ll probably get it from ecologists. [ed.: he didn't mention Boyle, but clearly he is influenced by Boyle's paper.] Says that the commons is not as bad off as the environment, b/c the commons was created intentionally and with a clear, self-conscious, long-term politics, whereas we exploited the environment for ages without clear understanding of what we were doing.

Biopatent protests are similarly politically motivated- goal is to demonstrate power/value of commons, and the damage caused by parcelization. The success of the movement is not predetermined; it requires determined, aware effort. “Can’t leave war to the generals or platform decisions to the platform makers.”

Governments now understand that commons is a reality, and has significant momentum, but we can’t be complacent. We are becoming more diverse, which makes political action hard, esp. since some of our allies are only allies of convenience.

From each according to ability is actually a possibility now in our domain; others before us did not really have the option, but we do and we should take it. This time we win.

Questions (really mostly just the answers):

  • By political he means civil/civilized- over coffee, in courtrooms, etc.- not in the street, nor by pushing for specific political candidates, since the fcc and doj are more important than top-level politicians, and appointments are also unpredictable. (Notes that both Gore and Bush made pilgrimage to Redmond in 2000, whereas he can’t imagine Teddy Roosevelt making a pilgrimage to Standard Oil.)
  • Thinks winning in open standards is long term- after 8-10 years most standards bodies are going to look like w3c, and have patent policies in place to enable them to escape from patent gaming.
  • Says the SFLC brief in Microsoft v. AT&T is identical to Eli Lilly’s brief; pharma is trying to throw software out of the patent tent before software takes down the whole thing.
  • Cites Rawls to justify the superior morality/justice of a sharing culture, with reference to the moral problem of keeping knowledge from the poor. (ed.: my political philosophy work pays off!)

19
Mar 07

Moglen speaking tonight

Thanks to the excellent InfoLaw NYC calendar, I just discovered that Prof. Moglen is speaking tonight at NYU Law School. The talk is titled “The Empire & the iPhone: ‘Technology Platforms,’ the Commons, and the Way We Live Now.” I’ll be going- hope to see folks there.

[Tangent: is there any way to get notifications when new events are added to a public/shared ical calendar? I would not have noticed this event if I hadn't had my own event to add to the calendar today.]


19
Mar 07

firefox nitpicks

When I mentioned I was switching from epiphany to ffox, I mentioned that I thought that epiphany still offered a better basic user experience. A couple friends asked me to elaborate, so here is an unordered list of things gathered over several days:

  • printing dialog: ephy’s is native; ffox’s is not native in Ubuntu’s build, and I hear it is even worse in the stock build. Not a huge deal, just ugly.
  • window icon: I found it very nice that ephy used the favico as the window icon; it was useful for finding relevant windows when alt+tab-ing.
  • history in new tab: when you open a link in a new tab in ephy, it inherits the history of the previous window, so that the back button works as you’d expect. This doesn’t work in ffox, and it drives me nuts.
  • direct bookmarks from url bar: in ephy, the url bar autocompletes not just from your history but from your bookmarks. This is huge once you’re used to it. (I hear fixing this is in the pipeline for ffox 3.)
  • bookmarks, generally: the hierarchical folders thing is so ’70s. Thankfully, ffox has the delicious bookmark plugin that rips and replaces the default ffox bookmarks, but by default ffox feels dreadfully primitive here, and even the delicious plugin feels clunky on occasion. (Again, I hear this is being fixed, but it should be a high priority.)
  • theming: I realize this will never really be fixed (unless GNOME switches to XUL) but it is still irritating that changing my GNOME theme does not change my firefox theme as well. The pseudo-themes people have put together are close but still irritating.
  • clutter/organization: not that ephy is perfect on either of these points, but I would love to see lots of ffox preferences nuked and some reorganization. Maybe I’m just too boring, but I never realized when I was using epiphany that one would want an entire page of preferences for tabs. (A ‘tab mode’ was mooted about on the ephy developer list, which made sense, but that was one checkbox, not six.) And I’d never think to find my list of cookies under preferences- that is a list of data; it should be under edit or view, not preferences.
  • polish on the little things: ffox has lots of things that feel like they were implemented slightly half-assedly- the hypothetically cool autocomplete from the search box, for example, is often useless (at least on a 1024×768 screen) because it shows you the text you’ve already typed, and all the suggested completions are hidden behind hyphenation. Suggested completions in the URL bar have similar issues- I get neither enough of the URL nor enough of the page title to actually be useful; just an often-identical fragment of each. These aren’t a big deal, but when you add up lots of little things like this, it gives the impression that ffox does not care much about polish, which will hurt them in the long run.

There are more, I’m sure, but now I’ve been using it too long to remember them :/


19
Mar 07

instead of post-it notes…

… next time you’re brainstorming, try a party. Nifty. Now I just need to find something to brainstorm about. :)

[Aside: I wonder how many people say 'still hungover' to twitter on Saturday and Sunday mornings?]


18
Mar 07

dinner

3 people + 3 1/2 bottles of wine = a nice dinner.

trow! krissa!


18
Mar 07

nice career advice

Great career advice in only about 30 seconds.


18
Mar 07

spring break (end vacation)

Sigh. Never long enough. High points/low points:

  • Love my half-siblings, so much that I woke up c. 7am on my vacation to drive them to school.
  • Love my step-siblings, so much that I watched two hours of American Idol with them. (Was actually fun. Not sure I’d ever become a regular, but I won’t avoid Idol-watching parties out of principle.) (One step-sister launched into a long rant on how broken voting for Idol is, which should give hope to my voting-oriented friends (Ben 1, Ben 2)).
  • Had several days of very productive reading of Constitutional Law. On my vacation. :/ But hey- very, very productive. So at least something good was salvaged.
  • Enjoyed being laptop-free.
  • Enjoyed being warm. Shorts. Sandals. Meals outside. Napped for an hour in a hammock strung between two palm trees, which is worth like a month of normal sleep.
  • My flight home got canceled. Had to spend another night in Miami. (Least exciting extra 24 hours ever spent in Miami, sadly. New haircut was the highlight.)
  • Missed Duke’s painful basketball loss while taking pictures of Chihuly in Fairchild Gardens. Was not completely thrilled with the results, but click to see them anyway ;)


18
Mar 07

productive testing tips

I was cited in an article on testing tips this past week. Here is some cut and paste from the email I sent to the author (Joe Barr) when he asked me for tips; my email goes into more detail than he was able to put in his article so I thought it might be worth posting.

  1. use a bugtracking system of some sort, and use as much metadata (including good titles) in that bugtracking system as you can. At first it is time-consuming, but over the long run, it’ll save you time by helping you avoid testing things or filing bugs twice. Relatedly, if we’re talking about things that can be done as a group, and not just as an individual, have a bugmaster- someone charged with organizing, sorting, and generally knowing what is going on with the bug tracker. That one person will help every other person who uses the bug tracker (both testers and developers) be more productive, which is invaluable.
  2. Where possible, use the very latest code. Don’t be afraid to rebuild things from CVS every night or every morning. The moreup-to-date your code is, the quicker you’ll catch things (again, helping everyone’s productivity) and the less time you’ll spend going back and forth with ‘is this in the latest version?’ Again, when speaking of a team, if someone can be charged with making this process as easy as possible, that one person has a productivity multiplier for the entire team- makes everyone more productive.
  3. If at all possible, write automated unit tests. The best way to be productive is to have the computer do the work for you. Again, this has up-front costs, but over the long run is a *huge* win. (If we’re talking about GUI software, try to focus on non-GUI code first when writing tests- GUI tests tend to be fragile, and you’re best off writing tests that will fail when things go badly wrong, not when a pixel shifted here or there.)
  4. dogfood, dogfood, dogfood. If at all possible, use the code you’re testing under real-life conditions to do everyday work. Real-life testing is always going to be more efficient than fake ‘do this, then do this, then do this’ checklist testing- that doesn’t catch edge cases, and it feels like work. If you’re using code for real work, you catch the edge cases that real users find, and you do it in the courseof doing something else- it doesn’t feel like work then. (Relatedly: if you dogfood and find a bug, make sure to do (1) file it immediately, and (3) write an automated test to duplicate the bug ASAP.)
  5. use automated crash reporting tools: every major OS now has ways to catch stack traces of catches and send them back to a bug database. Use those, and ship those- help the users help you.
  6. if you have an active volunteer community who are using nightly builds to do daily work, don’t spend your time testing things that they will inevitably test. For example, I’ve seen test plans that say things like ‘check to make sure it launches’. If it doesn’t run from the command line, a good community will let you know about it ASAP. If it crashes when you open the print dialog with 10,000 printers on your local network, well, most communities don’t run into that sort of thing- they have one printer. So spend your precious test cycles testing *that* kind of scenario, instead of testing basic stuff our community will catch like ‘does it start? does the file open dialog work?’

18
Mar 07

quick notes on using the N800 for a week

I left my laptop at home this week when I went on spring break, and used good old fashioned pen and paper for reading Con Law, and the N800 for everything else. Before I forget, a few notes:

  • if I could figure out how to get ogg support on this thing, I’d buy very large memory cards tomorrow. But so far the only docs I can find explaining ogg support are long and painful. With the very few mp3s I have (mostly from podcasts) this is a fairly capable replacement for my much-missed Rio.
  • text entry continues to be a major pain.
  • opera chokes to death on my planets. The new minimo build, unfortunately, is not much better (though otherwise quite nice.)
  • I need to see if I can use the N800 to grab/review photos- that was the one thing I really, really missed having the laptop for. (pictures soon.)
  • Otherwise, was quite useful for occasionally skimming my email and checking up on various little things- a very nice vacation tool.

11
Mar 07

my exciting spring break (a vacation message)

Next week is spring break, which is why I had time to cook and shop yesterday. I’ll be going to Miami, so I’ll be warm, but the theme for the week will be Con Law. Con Law. Also, more con law. Exciting, no?

I plan to do the work on paper, and for the first time in ages, leave the laptop at home. So I may be hard to reach. I’ll have my phone, and my N800, but with luck I’ll be ignoring them. See everyone next week.


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