Category Archives: FSF
King Canute famously failed to prevent the tide coming in. I can’t help wondering if Eben Moglen is setting himself on a similarly futile course, when he calls for decentralisation of our information infrastructure.
The subject of Moglen’s opening keynote at FOSDEM was liberty, and how technology can work for or against it. He spoke of current and recent topical events, from Wikileaks to the role of the ‘net in Egypt’s (so-far) peaceful revolution. And of how technology can serve those who might threaten freedom: how much sensitive information could a heavy-handed government pick up from something as simple as a legal action on Facebook. How Data Protection in Europe has merely served to outsource handling of personal data to countries like the US with no such protection of privacy.
His call to developers was to build decentralised networks, where we can publish, communicate, interact as we do on the ‘net without submitting all our data to any centralised database that might become the focus of malign attention. Examples of tasks he spoke of ranged from Facebook-style networking to building a citizens cellphone network from $20 base stations in people’s homes. Tasks which are at least technically feasible to prototype and develop.
Listening to this, my reaction was that he’s battling against history here. History on the ‘net has shown different media and channels becoming more, not less, centralised. The once-popular Usenet medium for public discussion has given way to web-based fora: a wholly inferior medium for the task, and one for which I must admit my small measure of guilt (though it seemed like an interesting thing to implement in 1995). IRC discussion remains popular amongst geeks, but elsewhere there came chatrooms, and now we even have Twitter making a grab for that space. Every time, the geek medium gives way to an inferior one because the latter gets the mindshare. Non-technical journalists will routinely invite us to ‘tweet’ them, or mention a web forum relevant to a topic under discussion, so the public learn of these media. Meanwhile the old, decentralised, shared, and in both these cases altogether superior, media are relegated to enclaves of geekdom (or, in the case of much of usenet, to wastelands of spam and other abuse). My suggestion to him was, you need to concentrate your efforts not so much on legislators, but on communicators. Journalists in mainstream media!
OK, ‘net history is short. Why should a campaigner for freedom not call for trends to be reversed?
A wider perspective tells us that the online centralisation trends of which I have written are merely examples of similar trends backed by far more history. The most striking parallel in English history is the Enclosure of the Commons. The absurd valuations given to some websites (headed by Facebook) tell us a new aristocracy is profiting from enclosing an online commons, albeit an ephemeral and transient one.
And I plead guilty to hosting my blog at another aristocrat of web-land, WordPress. Yep, my rantings are centralised as a matter of simple convenience.
The Free Software Foundation (FSF) has gone public with a statement on the Oracle vs Google litigation. The FSF is of course free to do so, and since it’s also a campaigning organisation we should not be surprised when they do. But does the statement itself stand up to scrutiny?
Before going any further, I should make it clear: this is a comment on the FSF’s position statement. No matter where this appears aggregated, I don’t represent anyone or anything other than myself. Any views I may have on the FSF itself, on Oracle or Google, on Java implementations, Android/Dalvik, on patents (software or otherwise) or on anyone/anything else, fall outside the scope of this posting. Nor should this be taken as comment on the FSF beyond this single document: as it happens, I am in general terms an admirer of the FSF.
The introduction is clear enough:
As you likely heard on any number of news sites, Oracle has filed suit against Google, claiming that Android infringes some of its Java-related copyrights and patents. Too little information is available about the copyright infringement claim to say much about it yet; we expect we’ll learn more as the case proceeds. But nobody deserves to be the victim of software patent aggression, and Oracle is wrong to use its patents to attack Android.
That’s fair: the FSF’s position against software patents is rational and consistent. Oracle vs Google is one of many patent cases currently in the courts throughout the rapidly-growing mobile devices space: some other household names that spring to mind include Apple, Nokia, HTC, and of course the victim of the biggest injustice, Blackberry-maker RIM. But it’s also fair to say Oracle vs Google may have more far-reaching repercussions than the others, insofar as it may affect Free Software in the Android ecosystem.
The second paragraph is more problematic:
Though it took longer than we would’ve liked, Sun Microsystems ultimately did the right thing by the free software community when it released Java under the GPL in 2006. […]
That’s fair as far as it goes, but it’s becoming a partisan statement within FOSS when you implicitly dismiss the ongoing controversy over licensing a TCK. The third paragraph goes on to say:
Now Oracle’s lawsuit threatens to undo all the good will that has been built up in the years since. Programmers will justifiably steer clear of Java when they stand to be sued if they use it in some way that Oracle doesn’t like. […]
Hang on! How is that new? The entire TCK issue is about field-of-use restrictions that are problematic for free software! At the same time, let’s not forget that Java was hugely popular among Free Software developers even before 2006: these controversies matter only to an activist minority.
If the above is nitpicking, paragraph 4 is altogether more suspect. Let’s quote it in full:
Unfortunately, Google didn’t seem particularly concerned about this problem until after the suit was filed. The company still has not taken any clear position or action against software patents. And they could have avoided all this by building Android on top of IcedTea, a GPL-covered Java implementation based on Sun’s original code, instead of an independent implementation under the Apache License. The GPL is designed to protect everyone’s freedom—from each individual user up to the largest corporations—and it could’ve provided a strong defense against Oracle’s attacks. It’s sad to see that Google apparently shunned those protections in order to make proprietary software development easier on Android.
Erm, this really is an attack on Apache! How would IcedTea have helped here? The only valid argument that it might have done is that rights were granted with Sun’s original code. I don’t think it’s clear to anyone outside the Oracle and Google legal teams whether and to what extent such ‘grandfather’ rights might affect the litigation. As far as licenses are concerned, the Apache License is a lot stronger on protection against patent litigation than the GPLv2 under which IcedTea is licensed. Indeed, in separate news, Mozilla (another major player in Free Software) is updating its MPL license, and says of its update:
The highlight of this release is new patent language, modeled on Apache’s. We believe that this language should give better protection to MPL-using communities, make it possible for MPL-licensed projects to use Apache code, and be simpler to understand.
Well, Mozilla is coming from a startingpoint closer to the GPL than Apache. It seems I’m not alone in supposing the Apache license offers the better patent protection, contrary to the FSF’s implication!
Finally the tone of the FSF statement, as expressed for example in the final paragraph, makes me uneasy:
Oracle once claimed that it only sought software patents for defensive purposes. Now it is using them to proactively attack free software.
Hmmm, attacking Android/Dalvik is proactively attacking free software? While it’s a supportable position it’s also (to say the least) ambiguous, and you haven’t made a case to convince a sceptic. Or a judge.
 Not to mention the grammar, up on which some readers of this blog will undoubtedly pick.