Register now at http://ict4dev.eventbrite.com/ - only 20 RSVPs available until we nail down a venue!
In Austin for SXSWi? A Geek? (ok, granted) Interested in changing the world? Building off of last year's amazing ICT4D meetup during SXSW, we're back at it this year with the second annual ICT4D Happy Hour: Geeks, Drinks, and Doing Good. We're also planning more than a day in advance this time (wow!).
We'll gather on Monday, March 14, 2011, starting around 5pm for a happy hour at a downtown watering hole (Hopefully the Gingerman like last year). Bring your favorite ICT4D toys (OLPCs, solar-powered GSM thingamajiggers, mHealth diagnostics and other gizmos) and your best ideas and inspiring innovations to talk about while sharing drinks with your colleagues from across the street and around the world.
Ashoka's Changemakers is running a global competition with the Omidyar Network to source the most innovative approaches for providing property rights to those who lack them around the world.
If you're reading my blog, you probable understand the importance of being able to define and claim your ownership of property - it affects the stability of your living situation, your ability to qualify for (micro)finance, and your ability to even get a job by having a "real" address. Not to mention the obvious personal dignity values of having a place you can call your home, and the hands-down value in women's land ownership in stabilizing communities.
As part of our competition process we let the world decide who among our finalists have the best ideas, giving everyone the ability to crown the winners. So go and read the ideas of the semi-finalists, create an account and vote for your favorites at http://www.changemakers.com/property-rights/semifinalists#tab-section
We are also supporting the development of new tools that enable citizens to exercise their rights of free expression by circumventing politically motivated censorship. We are providing funds to groups around the world to make sure that those tools get to the people who need them in local languages, and with the training they need to access the internet safely. [ ... ] We want to put these tools in the hands of people who will use them to advance democracy and human rights, to fight climate change and epidemics, [...]
Great ideals, sure, but what about WikiLeaks? Who in this day and age would vocally and publicly support tools that would "[circumvent] politically motivated censorship" when these crazies could be terrorists being censgored by a friendly government, or when their "free speech rights" could be potentially tied to copyrighted material?
WikiLeaks has changed political discourse, and quite possibly the path of the Internet's evolution. I can't claim to have completely digested my own views on this, but here's a start, and some links to a lot of great thoughtwork on the situation.
1) Maybe this is the world we want. Long discussions about the value of a hegemonic global political system and its values on stability (at the cost of human rights, generally speaking) aside, the USA's political power is in flux right now, and possibly fading out. Do we want another superpower to emerge and dominate the world? USA, for all our foibles, has some strong ideals around democratic rule and human rights. We don't always practice those, but they're at least core to our political discourse. A truly multipolar world needs global-level democracy, and it's tools like wikileaks that begin to create that. Well, that, and a roving band of crypto-anarchists who get pissed off at this ham-handedness and decide to take the websites of mastercard and visa down. And Wikipedia. And torrent-sharing sites. Any tool that's good at promoting human rights in repressive regimes is also good at enabling dissidents, whistleblowers, pedophiles, and people swapping mp3 files. You don't get to pick and choose who uses these things, and trying to do so destroys their value immediately. These tools also lend themselves towards mob rule, so we need to choose our next steps carefully. As a side note, if you really disapprove of harshly, externally-enforced transparency of what you consider private details, then I really hope you're not reading this from a link on Facebook.
2) It's OK to be a Voltaire here. While not technically his own words, he certainly held and espoused the concept: "I disapprove of what you say, but I will defend to the death your right to say it." Wikileaks is being, well, over the top and careless in what it's releasing. The Collateral Murder video seems pretty clearly whistleblowing. The cable leaks are un-aimed. Clay Shirky summed this up solidly:
I am conflicted about the right balance between the visibility required for counter-democracy and the need for private speech among international actors. Here’s what I’m not conflicted about: When authorities can’t get what they want by working within the law, the right answer is not to work outside the law. The right answer is that they can’t get what they want. [...]
Over the long haul, we will need new checks and balances for newly increased transparency — Wikileaks shouldn’t be able to operate as a law unto itself anymore than the US should be able to. In the short haul, though, Wikileaks is our Amsterdam. Whatever restrictions we eventually end up enacting, we need to keep Wikileaks alive today, while we work through the process democracies always go through to react to change. If it’s OK for a democracy to just decide to run someone off the internet for doing something they wouldn’t prosecute a newspaper for doing, the idea of an internet that further democratizes the public sphere will have taken a mortal blow.
It's OK, if not strongly encouraged, to be not a big fan of WikiLeaks, but still supportive of their right to exist and disseminate "leaked" information. Would the US be upset if this was a leak of internal Chinese diplomatic ramblings, or North Korea, or Iran -- or would we be chalking another success up for "the little guy" in the global struggle for democracy and freedom of speech? We're all sovereign States here, at some level, there should be at least an illusion of equal rights among States.
3) Don't be Grand Moff Tarkin. Yeah, a Star Wars reference for good measure. The actual reference is to some parting advice from Leia on his tough stance around the use of force to put down rebels; "The more you tighten your grip, Tarkin, the more star systems will slip through your fingers." As an anonymous commenter on the BoingBoing story above said;
I think you misunderstood what she said. The attacks are the tool. Just look at the effect its had on wikileaks. Its gone from being hosted on a single server with rather unsafe DNS etc to being mirrored over 1000 times across the world!
Truely this government is driving the development of anti-censorship tools and increasing the power of free speech online.
This is the first of many problems of this sort, and here we are showing off all the tricks in our playbook. Over at Crooked Timber, Henry puts it more succinctly:
The US response to Wikileaks has been an interesting illustration of both the limits and extent of state power in an age of transnational information flows. The problem for the US has been quite straightforward. The Internet makes it more difficult for states (even powerful ones such as the US) to control information flows across their own borders and others. [The jurisdictional problems of the Internet] makes it much harder for the US and other actors to use the traditional tools of statecraft[...]
However, there is a set of tools that states can use to greater effect. The Internet and other networks provide some private actors with a great deal of effective transnational power. Banks that operate across multiple jurisdictions can shape financial flows between these jurisdictions.
The Internet has this amazing and annoying problem that's baked pretty deeply in to its architecture - it is designed to move information as efficiently as possible. This makes censorship attempts backfire every time. Somehow, no one has learned this.
4) Shooting the messenger is a fast way to being uninformed. Disabling, hobbling, and otherwise subjecting tools to political will is a very dangerous path. Amazon has a great business around providing "elastic" computing and hosting services to companies, and I'm going to bet that anyone using Amazon's services is re-examining their hosting choices right about now. Breaking the DNS system to take the main wikileaks site off the web -- I'm sure that sounded like a brilliant idea, and it's going to reignite a debate around the US's control of huge swaths of the DNS system, and probably make that power very difficult to enact both politically and technically. Again, the trust in what was considered a trusty tool has been eroded, and anyone working on hot-button issues is going to take extra care such that they have secondary systems to provide future resiliency against a similar attack. Beyond the points made in (3), we're hurting normal business that trusts these services to be reliable. Ethan Zuckerman has a good Q&A about this at the Columbia Journalism Review
5) Don't forget the real story. Did Julian Assange actually commit a crime in the US? He's not a citizen, he didn't do any of this in the US, and he's not the one who stole the classified documents. And he hasn't been charged with a crime (in the US, yet). Are we really pursuing someone for re-broadcasting already leaked, classified documents? That worked so well with the Pentagon Papers.
Hey, at least we live in interesting times.
My brain was pretty close to silly putty by the end of last week. It was been snapping back and forth, rubber-band-like, between microscopic, tightly focused, gnarled and tricky use cases up to their connection to the UN Global Pulse project - a global, systems-changing project.
The Global Pulse, at scale, is... well, the more time I spend on it the less I'm sure I know what it specifically is. In effect, it is a massive data coordination system which helps visualization and tracking of anomalys and trends. The dream is to predict crises and improve prevention. This is easily thought of in detecting disease outbreaks through various data-connected behavior changes (increase in usage of oral rehydration salts as evidenced by stock-outs in health clinics reported in a nationa health information system could indicate a cholera problem). Its most valuable use case seems to be at the national level, but there would also (obviously) be a global level to track larger trends across countries and regions. And country-level offices could peer together with other Pulse installations, bring in global baseline data, and so on. It keeps going deeper and deeper in every direction possible.
Accepting the insanely complicated data and architecture questions, how do you even find the right data (whether it's well-formatted or a pile of paper), and connect it in and pull out solid anomaly tracking and generate useful, predictive guesses on trends. That's the key in the next stage of the Pulse - starting in one country. This PulseLab will be able to grok the local context and know the right data to plug in.
The trick for the data and architecture part has also been faced. Implementation will not be easy, by any means, but the goal of the architecture is to re-use and re-cycle as many existing tools as possible to slurp in data (both chunky databases and firehoses of live streaming data), standardize it, and then create a set of manipulation and visualization tools to help reveal trends and test hypotheses. This will likely take the form of a set of toyboxes of data sources, data transformation tools, apps (input/output to other useful systems like mappers, charting, Ushahidi, etc.), and a recipe box of how others have chained these together for specific data-digging goals. This recipe and the hypothesis testing tool (the "hunch" ) will likely compete to be the core social object of the system, with aid and government officials trading hunches and recipes (and recipes to support hunches, hunches based on recipe results...).
There is a lot up in the air, and a lot still to congeal as development of this tool and the architecture gets moving. The (amazingly well-facilitated) process which went from thinking through users, their requirements, common underlying system-level requirements and speccing those out was fantastic. It encouraged a lot of different and conflicting views around the product's end form to come to a loose consensus (and a better, more flexible product outline!).
If you're saying it can't be done, you're almost right. The first iterations will be limited and possibly fragile, relying on low-hanging data fruit instead of difficult to "harvest" data exhaust. Privacy issues abound, both on personal levels and at government security levels. Trust me when I say that the room was stock full of mind-bogglingly smart people who have dealt with the real worlds of development and reconstruction work, and these obstacles are being worked through by people who realize that lives and livelihoods are at stake in some of the privacy questions.
Here are summary notes from each day: One (Term of the Day: "Data Exhaust"), Two (TotD: "Data Esperanto"), and Three (TotD: "Contextualized Cartography"), as well as a solid overview of the project, and the call to action leading in to last week's workshop. A great writeup of the event is at by MIT's Nadav Aharony.
At #mHS10, we heard funders talking time and time again for letting "1000 flowers bloom" in mHealth pilots, and programs talking about pilots leading to more pilots. This was fine the first few times it came up, but by the last day, the syndromes of the pilot-itis pandemic were clear.
This reeks of desperation. The funders are not finding clear winners in their projects, and the various implementers are casting about with local solutions that they either can't or won't scale, trying to find an idea so powerful that it will break through this lock.
We need to focus more energy on innovations which are dealing with core problems in health and in using mobiles for health, and thin out some of these 1000s of flowers. The soil is too fertile for this approach, and the many duplicated, repeated pilots will crowd out new, creative and gamechanging ideas. We need to move past these more basic mhealth applications - reminder messages for drug adherence, pre-natal checkups and so on are great - but simply using a new communications method to address an old problem. Let's replicate and scale those to more sub-sectors and keep them funded, but let's not dwell on them.
On scale -- this is not something that's eay to do. There are many barriers in mobile and in health, from cultural concerns to be dealt with which limit scaling of health projects, to many technical ones inhibiting good mobile projects from being re-implemented in other regions. There are many good meta-solutions to the technical side - open data standards and open source, both praised often at MHS10, are paving the way by creating a variety of tools which can work together.
We need more.
The platforms and networks need to become more open. Projects have been able to thrive where they rely on the lowest common denominators in phones - voice and SMS. Even still, a lack of global short-codes and improved cross-carrier and cross-border functionality hinders scaling. Beyond voice and SMS, it becomes a difficult maze of twisty passages dealing with the various featurephone systems, vendor lock-downs, and even more capable smartphones, which are even more locked down and difficult to get custom applications loaded.
The building blocks are there -- open source tools and open data standards abound; focusing on those is a big first step. Banding projects together, connecting at events like the mHealth summit, and increased best-practice sharing is another. Not being shy about where the real blockers are to scalable solutions is the elephant in the room. Do we need to engage the GSMA and ITU to work on better cross-connection solutions among the many global connectivity providers? Cell phone manufacturers to improve standardized access to their devices? These aren't the low-hanging fruits, but they might be the keys.
Herein, a mix of quotidian tasks and big goals for us to prepare for a 2011 mHealth Summit. mHS10 was a great conference, and represents a seachange in the field compared to last year. It had a selection of amazing speakers, lots of academics and implementers, and overall just the right crowd.
Still, there remain some changes I'd love to see for the conference itself, and I'll follow up with some bigger challenges that the mHealth world needs to deal with, based on the themes from this year's conference.
First, keep the music if you must, but add lasers and a fog machine. If you were there, you know what I mean.
As you might have guessed from my tongue-in-cheek #mHS10 drinking game (pilot=1 shot, 1k flowers=2, feature phone=3, "going global with sms phone support" = finish bottle), I got a bit tired of "Pilot-itis," which was finally called out as a problem on stage by Christopher Bailey of the WHO during the Wednesday morning plenary.
This pilot-itis was my biggest overall frustration with the discussions and presentations this year - a seemingly endless march of "new" pilot programs around (1) SMS for outreach/awareness (2) SMS and mobile for low-touch scheduled reminders and interaction or (3) Apps for various forms of monitoring. Perhaps it's my relative unfamiliarity with the health field, but do programs do controlled studies every time they plan to release a new paper, or put a PSA ad at bus stops? There is so much that can be done today, with a few hours of hacking, to advance at least #1 and #2 above, settle on a few solutions, and move on to more impactful territory. Take a page from Nike (who have one of the most successful fitness monitoring apps in the wild) and Just Do It.
My recent blog post on Uruguay's Plan Ceibal generated a buzz of discussion over at OLPCNews on the value of measurement, test scores, and updates from the field on 1:1 laptop projects visibly impacting test scores (http://www.gse.uci.edu/person/warschauer_m/docs/netbooks-aera2010.pdf#n…). Are these soft measures of attendance and laptop usage good enough, or must we demand test score improvements?