How Wikipedia will save politics – by “Olga M”

As many ambitious young Yalies before me, I spent my summer working for a political organization in Washington DC. Jokes about the tech-cluelessness of politicians aside, I was amazed by the serious lack of reliable information on Capitol Hill. Congressmen got nearly all of their facts from lobbyists, either in direct conversations or in pseudo-objective policy papers written by those same interest groups. The voices of true experts and average citizens were completely drowned out in the cross-shouting of lobbyists and extremists.

That’s why I was so intrigued when my think tank started working on Progressive Map, a Wiki that is designed to provide Congressional staff with (left-leaning) reliable information on issues, organizations, and people. The project follows the trend of political Wikis, like conservapedia, liberapedia, and Rational Wiki, in creating collaborative information gathering projects dealing with political issues. Progressive Map differs in hoping that average citizens will be able to bypass lobbyists and the money-buying-access problem to tell their Congressmen the full truth about the people and policies they are dealing with.

Sounds like  a pipe dream, right?

On first glance, politics seems like the least likely field in which a Wiki format could work. For starters, the self-conscious norm for objectivity and consensus that make Wikipedia work are completely absent from politics. While Wikipedia relies on the basic notion of trusting your neighbor, politics encourages people to form adversarial groups that prove that their particular viewpoint is correct. If the average Wikipedia writer comes to engage in a common enterprise with other users, the average participant in politics just wants his policy to win, and consensus created on the Discussion page is not the way to do that.

Furthermore, the basic rules of Wikipedia are particularly hard to apply to politics. The no-original research policy is tricky in a field that deals primarily with people’s conjectures and expectations. For example, to say that the user thinks that the war in Afghanistan is hopeless would have to involve polling data specifying the demographic that believes in that argument, or else a link to a prominent commentator making that claim.

Meanwhile, the requirement of verifiability will inevitably run into disputes over credibility and representation. For example, is it appropriate to say that Republicans question the existence of global warming just because conservative Christian fundamentalists don’t believe in it? Political groups are by nature heterogeneous, and it is very hard (and potentially very anger-provoking) to generalize about their views.

Finally, the neutral point of view standard would require hard choices about what due and undue weight, as many very prominent political groups (e.g. LGBT groups) have small numbers of clear members and a much wider undefined support network.

Most damning, however, is the problem of editing by vested interests. Wikipedia works in part because few people care whether zucchini is a fruit or a vegetable, but questions of politics have lives and livelihoods at stake. The incentive to try to cheat the system is thus incredibly great.

Already, instances of interference abound in Wikipedia. Marty Meehan raised public outcry when he edited his own entry to delete a reference to a campaign promise, and staffers for many Congressmen admit to doing the same. The entry for President Obama had to be blocked from further editing, after too many birthers edited the page to question Obama’s birth certificate and sparked editing wars . Meanwhile, some blogs claim that there is already a conservative slant to Wikipedia because right-wing advocates are more willing to devote time to promoting causes.

These problems are not exceptions. A political Wiki would have to deal with more than just bored teenagers; it would have to face people who bomb abortion clinics, donate millions of dollars, and spend countless hours demonstrating for the sake of getting their viewpoint out there.

And yet for all of the obvious challenges, there is a glimmer of possibility that enough individuals who care about accountability and bipartisanship will join in on the project and make it work. The requirement for some final result may create a new culture in which users agree to represent others’ views fairly if they get the same treatment. Groups wishing to push their views will simply add a sentence that a particular person believes and advocates for a particular policy, while leaving the debate over the correctness of the beliefs to other spheres. Given how many voters seem disgusted with partisanship, the Wiki should have plenty of users who have a desire to preserve neutrality.

So how could we make Progressive Map work?

Wikipedia’s current format is clearly too trusting and open to prevent sabotage. An alternative could come from a system like Slashdot’s, which uses carefully chosen moderators among logged in and regular long-term users. They would be chosen, and would enforce, a system of Karma, in which comments are ranked from “Most Fair” to “Disruptively Biased.” Additionally, users could rate other users as “Disruptive,” alerting the moderators that a user is abusing the openness of the system. After a user makes a maximum number of disruptive changes, he or she would be blocked from the website.

Progressive Map has the chance to work, but it requires rules and sufficient participation to succeed.

Free and open source is not always the answer – by “Emily Y”

A recent New York Times article spotlighted a key issue in the world of open source software: businesses using others’ open source code to develop their own products and then failing to follow Open Source Standard (OSS) requirements. Open source issues such as these can be difficult – if not impossible – to overcome in the business sphere.  How can we expect programmers to put years of hard work into a quality program, and then just give it away for free?  But as its benefits to technological growth become increasingly obvious, open source software is becoming more common and accessible.  Is it possible for the future of software to be completely free and open source?

In the past, I’d been skeptical about of free software.  In respect to the quality, the free programs I’d downloaded and tested were fine, but never matched up to the caliber of (pricey) proprietary software programs.  More importantly, however, might have been that the phrase “open source” sounded like something that might appeal to a computer programmer, but not to me, a generally-technologically-capable-but-coding-oblivious student.  Why would I care whether or not I could access software code?

I’m not sure that I will ever have the desire to look at the coding of software.  What it comes down to is that some software on the market just doesn’t fit in a college student’s budget.  Moreover, most of this software is packed with features I’d never use, for techniques I’ll never understand.  When it comes to computers, I’m just a hobbyist.  For example, in working with newspaper design, I love toying around with the abundance of features that Adobe InDesign, Photoshop and Illustrator offer.  However, purchasing Adobe Creative Suite CS5 would set me back anywhere from $300 to $900 – and that’s the Student pricing.  Thinking about all of this led me to go the free route and test out a couple of “alternative” open source programs: GIMP and Inkscape, two major open source rivals to Adobe’s Creative Suite.

GIMP

GIMP is a free graphics manipulation program, with offerings similar to that of Adobe Photoshop.  In several ways, it lacks the power and usability of Photoshop.  Yet there are offshoots of GIMP that have used it to come awfully close to reproducing Photoshop.  The creator of GimPhoto took GIMP and modified it with features and a UI that rival those of Photoshop.  One major issue I held with GIMP was its inability to simply batch process a group of photos (automatically execute the same adjustments on several photos simultaneously).  According to the GIMP Wiki, in order to do this, the user must input commands, such as the one below:

(define (simple-unsharp-mask filename
radius
amount
threshold)
(let* ((image (car (gimp-file-load RUN-NONINTERACTIVE filename filename)))
(drawable (car (gimp-image-get-active-layer image))))
(plug-in-unsharp-mask RUN-NONINTERACTIVE
image drawable radius amount threshold)
(gimp-file-save RUN-NONINTERACTIVE image drawable filename filename)
(gimp-image-delete image)))

Which, to me, is closer to gibberish than a true “command.”

But still, the bottom line is that most of what GIMP doesn’t have, I wouldn’t use anyway.

Inkscape

Inkscape is the GIMP to Adobe Illustrator.  On most levels, Inkscape and Illustrator are identical when it comes to features.  There are a very small number of Illustrator features that are missing in Inkscape, but again, the people who makes use of these features are just a tiny fraction of the software’s users.   And the reverse is also true: Inkscape includes a number of useful features that are unavailable in Illustrator.  In fact, I found the Inkscape UI to be slightly more intuitive than Illustrator’s.   Thus, in my opinion, user interface and personal likings are what should influence one’s decision in this case.  Brand names are irrelevant.

A question often posed on the topic of open source software is whether or not computer programmers would continue to output quality software if there was no profit incentive.  But there is actually a great deal of profit to be made via free, open source software.  Where does the money come from?   Large companies such as Microsoft, Apple, and Google pay licensing fees to use open source software more freely.  For example, MySQL (an open source database) allows users to access and use its software at no cost; however, improvements that users make to the software must be shared with the company.  For individual users, this is generally a non-issue, but businesses rely on keeping the rights to their work to generate profit.  Thus, they pay these licensing fees, which can add up to significant profits for the original creator.

So why (or why not) open source?   There’s incredible room for enhancements in software, and with the increased freedom and flexibility of open source, the possibilities are endless.  Yet at the end of the day, I can’t use OpenOffice (sorry, Maria!).  I like the power of Microsoft Office, and I’m much more comfortable using it — no matter how annoyed I get with its UI changes.  Therefore, I understand if you can’t bear to make the switch to GIMP.  While we shouldn’t let our lives be controlled by proprietary software, we also shouldn’t impose limits on ourselves solely to promote open source.

In the end, a healthy balance between the two is really what we need.  There still is – and, I believe, always will be – a market for proprietary software.  Yet the major advancements made by open source software in the past decade are proof that open source is changing the way we create and use computer software.  The age of assuming “expensive software is better software” has passed; we are realizing that free software is no less advanced than proprietary software, while once-seemingly-impossible barriers to open source are gradually being overcome.

“A lot of people talk about open-source versus commercial, but they’re not mutually exclusive. Don’t view it as an all-or-nothing prospect.” — Steve Gerdt, program manager for open-source strategy at IBM.

Open Handset Alliance far from open by GNU standards – by “Bill T”

Like the previous blogger, I too am in love with my Droid. He is a Droid X. His name is Yeste (after the most famous swordmaker in all of Florin), and he runs Verizon/Motorola’s official OTA release of Froyo (Android 2.2) with Motorola’s MotoBlur skin on top of it. Motorola is a proud member of the “Open Handset Alliance” which is a group of 78 tech companies that seek to propagate Google’s open-source mobile operating system, “Android”. Some of its members are wireless distributors seeking wider access to smart phones, others are phone manufacturers looking to decrease some of its costs, others are developers excited about a popular mobile platform with a low bar for entry. All of them are in the business of technological advancements. All of them are in the business of making money. Many of them are competitors.

Google has set a tone of openness not entirely unlike that in GNU’s copyleft standards, but that tone ends at the conveyance of Android. As the leading producers of Android handsets, Motorola and HTC are the most capable of upholding the attitude of openness begun by Google. Motorola and HTC add the custom skins “MotoBlur” and “Sense UI” respectively  to Google’s stock form of Android, a practice Google adamantly defends, and one clearly aligned with GNU’s policy of allowing modification and redistribution (not that GNU’s rules apply to Android).

HTC has been moderately good about maintaining openness when conveying Android. Though they’ve added Sense, it’s possible to turn off most of it’s features and return to stock Android. Users seeking superuser access will still need to “root” their phones in order to load new firmware, but HTC hasn’t done much to prevent that. In fact, it’s become as easy as downloading an app to root HTC’s phones.

Motorola on the other hand, has shown a proclivity towards limitations on this openness. In order to remove MotoBlur, one must root one’s Motorola phone.  While rooting the Droid X and Droid 2 is possible, it is very difficult in comparison to other Android phones due to Motorola’s inclusion of a “Locked Bootloader” which, though it doesn’t “brick” the phone, takes very strong measures to prevent rooting. This ardent anti-circumvention measure would unquestionably violate copyleft standards, if they applied, and as a result, lowers the bar for openness among members of the Open Handset Alliance.

So what accounts for the difference between Motorola and believers in copyleft? Yes, Motorola is in the business of making money, but profit is not something the GPL disdains, indeed it embraces it by clarifying its definition of “free” as regarding freedom (which MotoBlur lacks) rather than price (which Motorola is happy to include). As the leading manufacturer of handsets, it can’t be that Motorola lacks interest in technological progress. Indeed, many consider Motorola’s Droid to be the first real “iPod Killer.”

Perhaps it’s the desire to beat the competition at either of these factors that drives Motorola’s desire to lock things down. While GNU supports gaining from modifications on open software, it doesn’t appear to support competitive enterprising. While GNU supports technological progress, that is not its primary tenant. Motorola’s desire, first, to lead the way rather than to contribute primarily to the customization of the Android platform is what pushes it so far away from the copyleft standard. Motorola doesn’t seem to want us to truly own the software on our phones.

I’m very happy with my MotoBlur-running Droid X, and even when given the warranty-preserving options of downloading MotoBlur-replacing apps like Launcher Pro or Handcent SMS, I’ve stuck with Motorola’s stock apps. I may not be better off for that, but I’m happy with those functions as they are. I don’t really need free tethering or mobile hotspot capabilities. With the ability to tether via Bluetooth to my MacBook Pro which can use its Airport as a hotspot, I’m satisfied. I don’t plan to root any time soon. Having said that, every once in a while I come across a cool app that says “requires root,” and wish that that wasn’t necessary. None of the apps have been worth voiding my warranty or taking the chance that I’ll brick my phone by screwing up the complicated process of circumventing eFuse, nor have they even been worth remembering. But as members of an Open Handset Alliance, perhaps Motorola should still consider democratizing superuser access.

After all, is there any good to the consumer from such a locked-down device?