Computers

Question Software Freedom Day‽

Saturday, September 15th, 2012

If software freedom is important, it must be attacked, lest it die from the unremitting bludgeoning of obscurity and triviality. While necessary, I don’t particularly mean trivial attacks on overblown cleverness, offensive advocates, terminological nitpicking, obscurantism, fragmentation, poor marketing, lack of success, lack of diversity, and more. Those are all welcome, but mostly (excepting the first, my own gratuitously obscure, nitpicking and probably offensive partial rant against subversive heroic one-wayism) need corrective action such as Software Freedom Day and particularly regarding the last, OpenHatch.

I mostly mean attacking the broad ethical, moral, political, and utilitarian assumptions, claims, and predictions of software freedom. This may mean starting with delineating such claims, which are very closely coupled, righteous expressions notwithstanding. So far, software freedom has been wholly ignored by ethicists, moral philosophers, political theorists and activists, economists and other social scientists. Software freedom people who happen to also be one of the aforementioned constitute a rounding error.

But you don’t have to be an academic, activist, software developer, or even a computer user to have some understanding of and begin to critique software freedom, any more than one needs to be an academic, activist, businessperson, or voter to have some understanding of and begin to critique the theory and practice of business, democracy, and other such institutional and other social arrangements.

Computation does and will ever moreso underlay and sometimes dominate our arrangements. Should freedom be a part of such arrangements? Does “software freedom” as roughly promoted by the rounding error above bear any relation to the freedom (and other desirables; perhaps start with equality and security) you want, or wish to express alignment with?

If you want to read, a place to start are the seminal Philosophy of the GNU Project essays, many ripe for beginning criticism (as are many classic texts; consider the handful of well known works of the handful of philosophers of popular repute; the failure of humanity to move on is deeply troubling).

If you want to listen and maybe watch, presentations this year from Jacob Appelbaum, Cory Doctorow (about, mp3), Eben Moglen (1, 2), and Karen Sandler (short, long).

Law of headlines ending in a question mark is self-refuting in multiple ways. The interrobang ending signifies an excited fallibility, if the headline can possibly be interpreted charitably given the insufferable preaching that follows, this sentence included.

Try some free software that is new to you today. You ought to have LibreOffice installed even if you rarely use it in order to import and export formats whatever else you may be using probably can’t. I finally got around to starting a MediaGoblin instance (not much to see yet).

If you’re into software freedom insiderism, listen to MediaGoblin lead developer Chris Webber on the most recent Free as in Freedom podcast. I did not roll my eyes, except at the tangential mention of my ranting on topics like the above in a previous episode.

Ride- and car-sharing and computers

Thursday, August 9th, 2012


Underemployed vehicles and land at Fruitvale BART parking lot, the 5th of 11 stations between me and Fremont.

Tuesday I attended Silicon Valley Automotive Open Source presentations on Car- and Ride-sharing. I heard of the group via its organizer, Alison Chaiken, who I noted in February gave the most important talk at LibrePlanet: Why Cars need Free Software.

The talks were non-technical, unlike I gather most previous SVAOS talks (this was the first event in Fremont, which is much more convenient for me than Santa Clara, where most previous talks have been held), but very interesting.

I did not realize how many car- and ride-sharing startups and other initiatives exist. Dozens (in Germany alone?) or hundreds of startups, and all manufacturers, rental companies, and other entities with fleets are at least thinking about planning something. That seems good on its own, and will provide good experience to take advantage of further more intensive/efficient use of vehicles to be enabled by robocars.

Carpooling and other forms of ride-sharing has gone up and down with fuel rationing and prices. Carsharing seems to go back to 1948 at least, but with slow growth, only recently becoming a somewhat mainstream product and practice. Ride- and car-sharing ought be complements. Sharing a taxi, shared vans, and even mass transit, could in some ways been seen as primitive examples of this complementarity.

Rationing is not in effect now, and real prices aren’t that high, so I imagine current activity must be mostly be a result of computers and communications making coordination more efficient. This is highlighted by the reliance and hope of startups and other initiatives on the web and mobile applications and in-car computers and communications for access, control, coordination, reputation, and tracking.

But none of this seems to be open source at the end-user service/product level. Certainly much or even most of it is built on open source components (web as usual, auto internals moving that way). These seem like important arenas to argue against security-through-obscurity in vehicles and their communications systems, and to demand auditability and public benefit for public systems in various senses (one of the startups suggested marketing their platform to municipal governments; if reputation systems are to eventually mediate day-to-day activities, they need scrutiny).

Libre Planet 2012

Tuesday, April 10th, 2012

2012-03-24%2009.44.38

A couple weeks ago I attended the Free Software Foundation’s annual conference, Libre Planet, held at UMass Boston a bit south of downtown. I enjoyed the event considerably, but can only give brief impressions of some of the sessions I saw.

John Sullivan, Matt Lee, Josh Gay started with a welcome and talk about some recent FSF campaigns. I think Sullivan said they exceeded their 2011 membership goal, which is great. Join. (But if I keep to my refutation schedule, I’m due to tell you why you shouldn’t join in less than 5 years.)

Rubén Rodríguez spoke about Trisquel, a distribution that removes non-free software and recommendations from Ubuntu (lagging those releases by about 5 months) and makes other changes its developers consider user-friendly, such as running GNOME 3 in fallback mode and some Web (an IceWeasel-like de-branded Firefox) privacy settings. I also saw a lightning talk from someone associated with ThinkPenguin, which sells computers pre-loaded with Trisquel.

Asheesh Laroia spoke about running events that attract and retain newcomers. You can read about OpenHatch (the organization he runs) events or see a more specific presentation he recently gave at PyCon with Jessica McKellar. The main point of humor in the talk concerned not telling potential developers to download a custom built VM to work with your software: it will take a long time, and often not work.

Joel Izlar’s talk was titled Digital Justice: How Technology and Free Software Can Build Communities and Help Close the Digital Divide about his work with Free IT Athens.

Alison Chaiken gave the most important talk of the conference, Why Cars need Free Software. I was impressed by how many manufacturers are using at least some free software in vehicles and distressed by the state of automotive security and proprietary vendors pitching security through obscurity. Like Appelbaum and Sandler, get Chaiken in front of as many people as possible.

Brett Smith gave an update on the FSF GPL compliance Lab, including mentioning MPL 2.0 and potential CC-BY-SA 4.0 compatibility with GPLv3 (both of which I’ve blogged about before), but the most interesting part of the talk concerned his participation in Trans-Pacific Partnership Stakeholder Forums; it sounded like software freedom concerns got a more welcome reception than expected.

ginger coons spoke about Libre Graphics Magazine, a graphic arts magazine produced entirely with free software. I subscribed.

Deb Nicholson gave a great, funny presentation on Community Organizing for Free Software Activists. If the topic weren’t free software, Nicholson could make a lot of money as a motivational speaker.

Evan Prodromou spoke on the Decentralized Social Web, using slides the same or very similar to his SXSW deck, which is well worth flipping through.

Eben Moglen’s talk was titled Free Software’s Future Amidst the Commercial Open Source Wars: How to Turn the Patent Disaster and Compliance Issues to Our Advantage, but I think I missed the how to part. Moglen also talked for awhile about IRS scrutiny of free software organization 501(c)(3) applications, vaguely hinting at a potential need to “re-evaluate how our infrastructure is organized” (paraphrase). I’ll have more to say about that, but in another post.

Chris Webber and I spoke about Creative Commons 4.0 licenses and free software/free culture cooperation. You can view our picture-only slides (odp; pdf; slideshare) but a recent interview with me and post about recent developments in MediaGoblin (Webber’s project) would be more informative and cover similar ground. We also pre-announced an exciting project that Webber will spam the world about tomorrow and sort of reciprocated for an award FSF granted Creative Commons three years ago — the GNU project won the Free Software Project for the Advancement of Free Culture Social Benefit Award 0, including the amount of 100BTC, which John Sullivan said would be used for the aforementioned exciting project.

Yukihiro ‘matz’ Matsumoto spoke on how Emacs changed his life, including introducing him to programming, free software, and influencing the design of Ruby.

Matthew Garrett spoke on Preserving user freedoms in the 21st century. Perhaps the most memorable observation he made concerned how much user modification of software occurs without adequate freedom (making the modifications painful), citing CyanogenMod.

I mostly missed the final presentations in order to catch up with people I wouldn’t have been able to otherwise, but note that Matsumoto won the annual Advancement of Free Software award, and GNU Health the Free Software Award for Projects of Social Benefit. Happy hacking!

Wincing at surveillance, the security state, medical devices, and free software

Friday, January 27th, 2012

Last week I saw a play version of . I winced throughout, perhaps due to over-familiarity with the topics and locale, and there are just so many ways a story with its characteristics (heavy handed politics that I agree with, written for adolescents, set in near future) can embarrass me. Had there been any room for the nuance of apathy, a few bars of Saturday Night Holocaust would’ve been great to work into the play. But the acting and other stuff making up the play seemed well done, I’m glad that people are trying to make art about issues that I care about, and I’d recommend seeing the play (extended to Feb 25 in San Francisco) for anyone less sensitive.

If you don’t feel like seeing a play in San Francisco, I recommend Jacob Appelbaum’s talk on surveillance, the security state, and free software at linux.conf.au 2012. It contains everything important Little Brother does and more, and isn’t fiction:

I also just watched Karen Sandler’s LCA talk, which I can’t recommend highly enough. It is more expansive than a short talk she gave last year at OSCON based on her paper Killed by Code: Software Transparency in Implantable Medical Devices.

I frequently complain that free/libre/open software and nearby aren’t taken seriously as being important to a free and otherwise good society and that advocates have completely failed to demonstrate this importance. Well, much more is needed, but the above talks give me hope, and getting Appelbaum and Sandler in front of as many people as possible would be great progress.

Years of open hardware licenses

Tuesday, January 10th, 2012

Last in a list of the top 10 free/open source software legal developments in 2011 (emphasis added):

Open Hardware License. The open hardware movement received a boost when CERN published an Open Hardware License (“CERN OHL”). The CERN OHL is drafted as a documentation license which is careful to distinguish between documentation and software (which is not licensed under the CERN OHL) http://www.ohwr.org/documents/88. The license is “copyleft” and, thus, similar to GPLv2 because it requires that all modifications be made available under the terms of the CERN OHL. However, the license to patents, particularly important for hardware products, is ambiguous. This license is likely to the first of a number of open hardware licenses, but, hopefully, the open hardware movement will keep the number low and avoid “license proliferation” which has been such a problem for open source software.

But the CERN OHL isn’t the first “open hardware license”. Or perhaps it is the nth first. Several free software inspired licenses intended specifically for design and documentation have been created over the last decade or so. I recall encountering one dating back to the mid-1990s, but can’t find a reference now. Discussion of open hardware licenses was hot at the turn of the millennium, though most open hardware projects from that time didn’t get far, and I can’t find a license that made it to “1.0″.

People have been wanting to do for hardware what the GNU General Public License has done for software and trying to define open hardware since that timeframe. They keep on wanting (2006) and trying (2007, 2011 comments).

Probably the first arguably “high quality” license drafted specifically for open hardware is the (2007). The CERN OHL might be the second such. There has never been consensus on the best license to use for open hardware. Perhaps this is why CERN saw fit to create yet another (incompatible copyleft at that — incompatible with TAPR OHL, GPL, and BY-SA), but there still isn’t consensus in 2012.

Licenses primarily used for software (usually [L]GPL, occasionally BSD, MIT, or Apache) have also been used for open hardware since at least the late 1990s — and much more so than any license created specifically for open hardware. CC-BY-SA has been used by Arduino since at least 2008 and since 2009.

In 2009 the primary drafter of the TAPR OHL published a paper with a rationale for the license. By my reading of the paper, the case for a license specific to hardware seems pretty thin — hardware design and documentation files, and distribution of printed circuit boards seem a lot like program source and executables, and mostly subject to copyright. It also isn’t clear to me why the things TAPR OHL handles differently than most open source software licenses (disclaims strictly being a copyright license, instead wanting to serve as a clickwrap contract; attempts to describe requirements functionally, instead of legally, to avoid describing explicitly the legal regime underlying requirements; limited patent grant applies to “possessors” not just contributors) might not be interesting for software licenses, if they are interesting at all, nor why features generally rejected for open source software licenses shouldn’t also be rejected for open hardware (email notification to upstream licensors; a noncommercial-only option — thankfully deprecated late last year).

Richard Stallman’s 1999 note about free hardware seems more clear and compelling than the TAPR paper, but I wish I could read it again without knowing the author. Stallman wrote:

What this means is that anyone can legally draw the same circuit topology in a different-looking way, or write a different HDL definition which produces the same circuit. Thus, the strength of copyleft when applied to circuits is limited. However, copylefting HDL definitions and printed circuit layouts may do some good nonetheless.

In a thread from 2007 about yet another proposed open hardware license, three people who generally really know what they’re talking about each wondered why a hardware-specific license is needed: Brian Behlendorf, Chris DiBona, and Simon Phipps. The proposer withdrew and decided to use the MIT license (a popular non-copyleft license for software) for their project.

My bias, as with any project, would be to use a GPL-compatible license. But my bias may be inordinately strong, and I’m not starting a hardware project.

One could plausibly argue that there are still zero quality open hardware specific licenses, as the upstream notification requirement is arguably non-open, and the CERN OHL also contains an upstream notification requirement. Will history repeat?

Addendum: I just notice the existence of an open hardware legal mailing list, probably a good venue to follow if you’re truly interested in these issues. The organizer is Bruce Perens, who is involved with TAPR and is convinced non-copyright mechanisms are absolutely necessary for open hardware. His attempt to bring rigor to the field and his decades of experience with free and open source software are to be much appreciated in any case.

Rolling bugfree‽

Sunday, December 4th, 2011

Since September 26 I’ve been exclusively using Firefox Nightly builds. I noticed an annoying bug a few days ago. It was gone the next day. It occurred to me that I hadn’t noticed any other bugs. For months prior, I had used Firefox Aurora (roughly alpha) and don’t recall any bugs.

Since October 15 I’ve been using Debian Testing on my main computer. No problems.

For years prior, I had been using Ubuntu, and upgrading shortly after they released an alpha of their next six-month release. Years ago, such upgrades would always break something. I upgraded an older computer to the just released Ubuntu 12.04 alpha. Nothing broke.

In recent memory, final releases desktop software would often crash. Now, there are as many “issues” as ever, but they seem to be desired enhancements, not bugs. The only buggy application I can recall running on my own computer in the last year is PiTiVi, but that is just immature.

Firefox and Debian (and the many applications packaged with Debian) probably aren’t unique. I hope most people have the relatively bug-free existence that I do.

Has desktop software actually gotten more stable over the last 5-10 years? Has anyone quantified this? If there’s anything to it, what are the causes? Implementation of continuous integration testing? Application stagnation (nothing left to do but fix bugs — doubt it!)? A mysterious Flynn Effect for software? Or perhaps I’m unadventurous or delusional?

Us Autonomo!

Monday, July 14th, 2008

Autonomo.us and the Franklin Street Statement on Freedom and Network Services launched today.

I’ve written about the subject of this group and statement a number of times on this blog, starting with Constitutionally Open Services two years ago. I think that post holds up pretty well. Here were my tentative recommendations:

So what can be done to make the web application dominated future open source in spirit, for lack of a better term?

First, web applications should be super easy to manage (install, upgrade, customize, secure, backup) so that running your own is a real option. Applications like and have made large strides, especially in the installation department, but still require a lot of work and knowledge to run effectively.

There are some applications that centralizaton makes tractable or at least easier and better, e.g., web scale search, social aggregation — which basically come down to high bandwidth, low latency data transfer. Various P2P technologies (much to learn from, field wide open) can help somewhat, but the pull of centralization is very strong.

In cases were one accepts a centralized web application, should one demand that application be somehow constitutionally open? Some possible criteria:

  • All source code for the running service should be published under an open source license and developer source control available for public viewing.
  • All private data available for on-demand export in standard formats.
  • All collaboratively created data available under an open license (e.g., one from Creative Commons), again in standard formats.
  • In some cases, I am not sure how rare, the final mission of the organization running the service should be to provide the service rather than to make a financial profit, i.e., beholden to users and volunteers, not investors and employees. Maybe. Would I be less sanguine about the long term prospects of Wikipedia if it were for-profit? I don’t know of evidence for or against this feeling.

Consider all of this ignorant speculation. Yes, I’m just angling for more freedom lunches.

I was honored to participate in a summit called by the Free Software Foundation to discuss these issues March of this year, along with far greater thinkers and doers. Autonomo.us and the Franklin Street Statement (named for the FSF’s office address) are the result of continued work among the summit participants, not yet endorsed by the FSF (nor by any other organization). Essentially everything I conjectured above made it into the statement (not due to me, they are fairly obvious points, at least as of 2008, and others made them long before) with the exception of making deployment easier, which is mundane, and service governance issues, which the group did discuss, but inconclusively.

There’s much more to say about this, but for now (and likely for some time, at the rate I write, though this activity did directly inspire me to propose speaking at an upcoming P2P industry summit, which I will early next month–I’m also speaking tomorrow at BALUG and will mention autonomo.us briefly–see info on both engagements) I wanted to address two immediate and fairly obvious critiques.

Brian Rowe wrote:

“Where it is possible, they should use Free Software equivalents that run on their own computer.” This is near Luddite talk… It is almost always possible to use an app on your own comp, but it is so inefficient. Networked online apps are not inherently evil, should you back up your work
offline, yes. Should you have alternative options and data portability, yes. You should fight to impove them. But you should not avoid them like the plauge.

The statement doesn’t advocate avoiding network services–see “Where it is possible”, and most of the statement concerns how network services can be free. However, it is easy to read the sentence Rowe quoted and see Luddism. I hope that to some it instead serves as a challenge, for:

  • Applications that run on your own computer can be networked, i.e., P2P.
  • Your own computer does not only include your laptop and home server, but any hardware you control, and I think that should often include virtual hardware.

Wes Felter wrote:

I see a lot about software licensing and not much about identity and privacy. I guess when all you have is the AGPL everything looks like a licensing problem.

True enough, but lots of people are working on identity and privacy. If the FSF doesn’t work on addressing the threats to freedom as in free software posed by network services, it isn’t clear who would. And I’d suggest that any success free software has in the network services world will have beneficial effects on identity and privacy for users–unless you think these are best served by identity silos and security through obscurity.

Finally, the FSF is an explicitly ideological organization (I believe mostly for the greater good), so the statement (although not yet endorsed by the FSF, I believe all participants are probably FSF members, staff, or directors) language reflect that. However, I suspect by far the most important work to be done to maintain software freedom is technical and pragmatic, for example writing P2P applications, making sharing modified source of network applications a natural part of deployment (greatly eased by the rise of distributed version control), and convincing users and service providers that it is in their interest to expect and provide free/open network services.

I suggest going on to read Evan Prodromou (the doer above) on autonomo.us and the Franklin Street Statement and Rufus Pollock on the Open Software Service Definition, which more or less says the same thing as the FSS in the language of a definition (and using the word open), coordinated to launch at the same time.

Commoditizing the cloud

Wednesday, April 9th, 2008

Doug Cutting on Cloud: commodity or proprietary?:

As we shift applications to the cloud, do we want our code to remain vendor-neutral? Or would we rather work in silos, where some folks build things to run in the Google cloud, some for the Amazon cloud, and others for the Microsoft cloud? Once an application becomes sufficiently complex, moving it from one cloud to another becomes difficult, placing folks at the mercy of their cloud provider.

I think most would prefer not to be locked-in, that cloud providers instead sold commodity services. But how can we ensure that?

If we develop standard, non-proprietary cloud APIs with open-source implementations, then cloud providers can deploy these and compete on price, availability, performance, etc., giving developers usable alternatives.

That’s exactly right. Cloud providers (selling virtualized cpu and storage) are analogous to hardware vendors. We’re in the pre-PC era, when a developer must write to a proprietary platform, and if one wants to switch vendors, one must port the application.

But such APIs won’t be developed by the cloud providers. They have every incentive to develop proprietary APIs in order to lock folks into their services. Good open-source implementations will only come about if the community makes them a priority and builds them.

I think this is a little too pessimistic. Early leaders may have plenty of incentive to create lockin, but commoditization is another viable business model, one that could even be driven by a heretofore leading proprietary vendor, e.g., the IBM PC, or Microsoft-Yahoo!

Of course the community should care and build the necessary infrastructure so that it is available to enable a potential large cloud provider to pursue the commoditization route and to provide an alternative so long as no such entity steps forward.

Cutting has been working on key parts of the necessary infrastructure; read the rest of his post for more.

End Software Patents

Sunday, March 2nd, 2008

I strongly prefer voluntary action. However, software patents are not amenable to workaround and so must be attacked directly through less savory legal, legislative, and electoral routes (though if software patents are toxic to free software, the opposite is also true, so simply creating and using free software is a voluntary if indirect attack on software patents).

Software patents are the major reason multimedia on the web (and on computers generally) is so messed up — few multimedia formats may be implemented without obtaining many patent licenses, and amazingly, this is sometimes impossible:

[The framework] is so patent-encumbered that today no one really knows who has “rights” to it. Indeed, right now, no new MPEG-4 licenses are even being issued.

As the End Software Patents site emphasizes, software patents negatively impact every sector now that everything uses software.

My only problem with the ESP site (and many others, this is just a general peeve of mine) is that it does not even link to similar resources with a non-U.S. jurisdiction focus. For example, the What Can I Do? page might state that if one is reading the page but not in the U.S. (because that never happens), please check out FFII (EU) and similar.

In any case, please join the effort of ESP and others to eradicate software patentsweapons of mass destruction. Ars Technica has a good introductory article on ESP.

LimeWire popularity

Sunday, December 16th, 2007

I continue to be intrigued by ‘s huge and relatively unsung popularity. According to a December 13 release:

More than one-third of all PCs worldwide now have LimeWire installed, according to data jointly released by Digital Music News and media tracking specialist BigChampagne. The discovery is part of a steady ascent for LimeWire, easily the front-running P2P application and the target of a multi-year Recording Industry Association of America (RIAA) lawsuit. For the third quarter of this year, LimeWire was found on 36.4% of all PCs, a figure gleaned from a global canvass of roughly 1.66 million desktops.

The installation share is impressive, and unrivaled. But growth has actually been modest over the past year. LimeWire enjoyed a penetration level of 34.1% at the same point last year, a difference of merely 2.3%.

These figures don’t jibe with those supposedly from the same parties from earlier this year, which found LimeWire installed on 18.63% of desktops. A writer on TorrentFreak who has presumably seen the more recent report (US$295, apparently including the requisite section titled “LimeWire Challenged by…Google?”) says:

From the data where the report is based on we further learn that Limewire’s popularity is slowly declining. However, with an install base of almost 18% it is still the P2P application that is installed on most desktop computers. Unfortunately Digital Music News has trouble interpreting their own data, they claim in their press release that it is 36.4%, but that is the market share compared to other P2P clients (shame on you!).

In other open source filesharing application news, made its first release in over two years on December 1.

Via Slyck.