A month in Nairobi

Background of the gig

Pablo and games

I met this guy named Pablo Suarez in a pub in Boston, when our mutual friend John Crowley insisted I leave my introvert-hole. When John insists, I tend to listen. And as always, it was totally worth it. Pablo plays games. As a climate scientist, he got tired of people falling asleep in meetings. He was aware of the direness of the situation, but no one else felt the same urgency. So he started expressing probability and costs and delays through dice, and beans, and objectives. He’s played these games with people who live in disaster-prone areas on through people at the UN who make policy about resource allocation. He’s created actual, connected change through an entire system. We’ve since embarked upon a few event adventures together, and I’m glad to call him friend and cohort.

My experience with KRCS

And so I met this guy named Dr James Kisia, when Pablo suggested I take a gig at the Kenyan Red Cross. In a continuing trend, when Pablo suggests things, I tend to listen. James has become well known as an innovator in the NGO/innovation space. As an example, reframing the understanding and practice of social entrepreneurship in resource-poor settings. Exploring sustainable resource mobilization for an organization whose relevance in disaster-prone Kenya is increasingly becoming apparent. The KRCS runs 3 hotels in Kenya, taking advantage of the fact that conferencing is a major business in Kenya, and in Nairobi particularly. It might seem paradoxical, having a five star facility on the campus of the a humanitarian organization, but the money the hotels make is ploughed back into the humanitarian work of the organization — including non-funded sudden onset disasters.

Based entirely on good faith, shoe strings, and a few well-placed calls, James and I embarked upon a trust fall with each other, based entirely on Pablo’s word. The Web of Trust in real life. I arrived to Nairobi for 4 weeks of work with little guidance beyond to lay groundwork for a Dadaab-focused intern or contractor, as specific to what would be applicable to climate change issues as well. Continue reading

Another Whirlwind Tour

The Bank booked my tickets for me (yay no financial overhead!.. but–) with an 11-hour layover at LHR. So I popped on the Heathrow Express to Paddington. I’m sitting in a Starbucks, of all places. They’re playing Morrisey. It’s pretty awful, but it’s also a holiday and everything else around here was closed. I was meant to have been back in Boston for the past week, after a long stint of travel, but things got extended by a continent, so here I am.


I gave a keynote at Cascadia.JS, and the event and its people were absolutely wonderful. Even played some pinball with Case (oh, PS, we’re throwing a CyborgCamp at MIT in October and you should come). I was soooo stressed when I gave this talk. Not from the talk itself – this community is lovely! I even wrote about it on the Civic blog – but because of the things surrounding this entry. When I watched the video later, it’s actually pretty alright. They gave me a full 30 minutes, and I wish I had padded it with more information. C’est la vie. Huge huge hugs to Ben and Tracy and the rest of the crew. You made a rough time easier through your care.

The drawings I did for other people’s talks are all here.


This was my first Wikimania, and it was stunning. So so much fun. Many things to think about, frustrations in new light, conversations over cider, and even more stick figures. And! Some lovely person taught me how to upload my drawings to the commons, and so now I’ll be hosting from there instead of from Flickr. Got to spend too-short time with Laurie (who I’ll see more of in Boston! Yay!), AND found out about Yaneer’s work on networked individuals and complex systems which rings closer to true in my intuition than most anything else I’ve run across recently.

Getting to know a neighborhood in London that I actually like, with art in the alleys and a bike repair and tailoring shop with a pub and wifi while you wait that is totally hipster gentrification and I so don’t care. And a strange moment in a Bombay-style restaurant of a half-recognized face, that ends up being the brother of the heart-based Seattle ex-Partner. We hug fiercely (as is the way of his family, and mine), until his manager gets angry. We laugh and promise to catch up.

Thence to Future Perfect, through the too-early fog of morning, and a panic attack, and dear Sam handling the accompanying compulsive need to stick to The Plan, even if it did not make the most sense, with the sort of calm curiosity and fondness which is exactly what is needed in those moments, and jogging through far away airports to finally arrive at our not-even-yet-boarding gate.

Future Perfect

A short flight (slept through) and a longer ferry ride (also slept through) through the archipeligos of Sweden, and Sam and I are on the island of Grinda for Future Perfect. We’re here at the behest of one Dougald Hine, long-time mirror-world not-quite-yet-cohort, to be Temporary Faculty at the festival, and to “difficultate.” It’s a strange thing, to be encouraged to ask the hard questions, and Ella and I are a bit adrift in the new legitimacy of our usual subversive action. “Ella, I think we’ve just been made legible.” “Shit. Quick, act polite!” But there’s an awfully strong thread of Libertarianism and Profiteering From The Future, so it’s not a difficult thing to ask stir-up questions. I sit on a panel called When Women Run the World, and mock the title, and question the assumption of binary sex, and point out matrixes of power. I draw as people talk, and post the print-outs to a large board for all to see, a strange combination of digital and analogue. Another panel I’m pulled onto I advocate for inclusion and codesign on the basis of values – not everyone bites. So then, pulling from Yaneer’s work, I point out that hierarchies fail at the capacity of any individual, whereas examined networks can scale in complexity. They nod. I grit teeth.

We also meet Bembo and Troja Scenkonst and Billy Bottle and Anna and the Prince of the Festival Lucas, and see old friends Ben and Christopher and Smari. We walk through the cow and sheep pasture as a shortcut from breakfast to festival, avoiding dirty boots and communicating via body language to over protective rams. I jump into the half-salt water of the archipelagos after a long sauna stint, and we drink sweet Swedish cider, and we sing Flanders and Swann across our joined repertoires. Ed gives me access to his audio book library, and I’m high on dopamine and scifi for hours to come. Our tiny temporary faculty crew sleeps in adjacent cabins, keeping the floors swept and porches clean.

And another early flight, stomach dropping as the pre-booked taxi service couldn’t find us and didn’t speak English (and Sam doesn’t hold Swedish in his repository of languages), no Ubers showing up on the app as they had the previous night, and finally finding a taxi app that would generate our location and sent a lovely driver for us. Getting to the airport, again, in time, with an uncertainty of how to part ways from this other human-shaped being who moves at high velocities, having been caught up in each other’s orbits for a short period of time, still texting threads and punctuation past gates.


And then I went back to Dar. And I realize in writing this how worn down my travel-muscle is, exhausted to the core. Less able to appreciate the beauty of a second wrecked ship on a calm sandy beach, unable to see the trying and hurt at the core of some of the people we hear speak. I am frustrated that the workshop I have been flown here to participate in has people reading verbatim from slides, that at the core of this workshop are not the people who are the most marginalized. I am brief, and I am blunt, and I do not show the same care that I expect to be shown to everyone. I become even more blunt with those who are unkind to others, a sort of brute force function into civility, and I and others know it will not work.

But some of the workshop has us figuring out hairy problems like reducing the 16-digit identifier for water points to locally useful and uniquely identifiable phrases for the database lookup table. I listen while the People Who Decide These Things think their servers won’t have the troubles other servers have. And some sections have people talking about appropriate technology and inclusion. It is productive, though differently than I’m used to.

I exchange a quiet conversation in the front of a taxi that waited for us at a restaurant, a practice which I hate, on the long journey home. The driver having not said more than a word or two at a time at first, now sharing anger about high taxes and now visible payout. The roads are paid for by other countries, the buildings, the power grid… where are his tax dollars going? We talk about schools, and his sister, and about how he has no way to speak.

We work with the Dar Taarifa team, who are unfolding and learning to push back, hours into github and strange google searches and odd places to encourage and odder places to encourage disagreement. We pause for translations, and I try to bow out so they’ll operate at full speed in Swahili, rather than moving slower so that I might understand.

Oh, also:

One of my drawings ended up all over the place:

Morgan’s research is pretty boss, and Barton did a great job writing.

It looks like I’m going to be in Kenya in parts of October and November playing games around climate change.
This post is apparently in the memory of LJ.

Adventures in Government Grants

Over at Geeks Without Bounds, we’re working on filing some grants, including with the USG, and that involves a convoluted process of website registrations, number assignations, and security nightmares.

The site you use to register for your DUNS-number (which stands for Data Universal Number System. What I don’t event.) emailed me my password in plaintext.

The next site in this process asked for a password to act as my sig – exactly 9 LETTERS long, in plaintext. I made that password “plaintext” just for kicks. You might as well know, because it’s just hanging out there anyway. And it’s far more complicated to figure out which address they’re asking for at any point on a form than it would be to crack.

That same site called me the executor of consent, which is pretty badass, and makes me hope the USG might be starting to consider enthusiastic consent from the governed.

I was then asked to enter my CAGE. Which I did not consent to.

Screen Shot 2014-07-24 at 10.19.21 AM

Responsible Project Lifecycle

We’re thrilled to announce our first white paper, inspired by the Engine Room’s Responsible Data Forum in Oakland months ago, and with interviews with Heather, Sara, Max, and Lisha!

Responsible Humanitarian And Disaster Response Project Cycles : Embed a “kill date” on your PLATFORM. If people are using that platform, this becomes a part of the community and culture. Alternatively, create a set of stages for the platform. For example, a crisis platform could have the following stages: initial situation awareness, crisis response, early recovery, recovery, and handover. Each of these stages have different information needs and different/progressively more restrictive rules that can be applied. Stages can have expected transition dates relative to each and informed by the unique situation needs. The most important lesson to learn is that there is no easy mandate. Each event will change the needs/time required to complete tasks, and is informed by engaging and communicating with all portions of the community (mappers, in-field deployments, affected populations, etc.).

What Response Can Learn from Co-Ops

I had an amazing chat with Emily M Lippold Cheney after meeting serendipitously at a Libre Fest in Cambridge. She agreed to do a GWOBcast on the overlap of digital response and the history of cooperatives. It reminded me a bit about the Brainmeats Lisha and I did awhile ago on The Culture of Eviction.


  • ACDI-VOCA: Coops in Crisis Response Paper (.pdf): This is an international cooperative development org largely funded by USAID, so it uses a democratic model within an not-so-democratic development industry.
  • Isla Vista Community Network: This is the group that just started meeting together in an unincorporated area and, by sheer persistence and existence, started being seen as a representative body that had some authority. Recently, through the work of this network and some of its members, the community was able to save some buildings from being demolished by the County and have the turned into (much needed) community centers. The IVCN is going to be meeting and taking the lead on deciding the how/who of using the buildings.


Technology as a Means to Equality

Originally posted on Geeks Without Bounds

I had the honor recently of speaking at the Médecins Sans Frontières (MSF / Doctors Without Borders) Canada Annual General Assembly (AGA). While an international organization, each location has a very large group of people who work on decision and policy for their specific group for the year – usually in the AGA. These are three days of talks, debates, and dinners. The international group defines a focus for the discussions, but it’s up to each pod how they act around that focus. This year, it was how MSF is using (or not) technology. While most of the talks were internal, the bit of time I was there the topics ranged from telemedicine to social media in conflict zones. They asked I come speak about technology and disaster/humanitarian response.

The gist of the talk I gave (15-minute video follows) is that technology is a means to more equality in the world – a way to be inclusive. That there are many people in the world who want to use their technical skills to help groups like MSF out, but we absolutely need them at things like hackathons. That there are many people with voices and connections to the globe now, and that groups like MSF have a responsibility to listen to them directly. And that technology, when done in codesign, will be aligned with what their needs are, and is an ongoing relationship, not a one-off delivery.

Again, most all of the discussion happened behind closed doors, but I recorded my laptop and voice while I did my own presentation.

It seemed to go pretty well. We’re keeping the conversation going, and I’m excited for more points of connection. You can follow the prezi at your own pace here, and see the full #vizthink for the panel here.

Some other highlights:
The other exceptional panelists and myself advocated for F/OSS, especially in light of security, for inclusion. MSF is rightfully anxious about infiltration, ways to be transparent, and usability. Ivan and I re-emphasized open source communities, that people are committed to examining (and re-examining) code for backdoors and optimizations. That open source has been around for decades, that most technology is built upon it, and that it’s a way of performing mutual aid between countries and cultures.

Someone asked in Q+A about using things like Facebook and Twitter in the field, if use could cause problems. Problems of location or images suddenly not being as private as you thought, and kidnappings and killings resulting. Or, what if things just get hacked by governments or by insurgents? My response was that MSF, with all their weight and influence in the world, has a duty to insist upon things like Coercion-Resistant design. Insist that these companies treat their customer bases humanely.

Everything Wrong With How to Write Things Up In One Entry

I was just heading back from a week in Dar es Salaam and Iringa District when a bunch of people I <3 filled up my inbox. “Have you seen this thing? Isn’t that what you’re in Tanzania for?” Yes. Which made me sigh, because all the updates about this deployment and the community development have been blogged at the Taarifa and GWOB websites. Sometimes it’s easiest to uphold the very vacuum chamber lamented, rather than do DuckDuckGo searches. Nor did the author reach out to the existing community before complaining about… the lack of community… which is amusing as those two things cover most of what the write-up is about.

But maybe I’m tired from travel. 11 hours in a car to catch a 7 hour flight that was delayed enough that I wrote this while standing in the Istanbul airport sorting out a new route to North America. And all I can think is, “is this blog entry worth my time?” But as it gets to a deeper crux, I’ll go for it. From the article, Everything Wrong in ICT4D Academia in One Research Paper:

  1. Focusing on Westerners: The paper starts with a long detail about a Random Hacks of Kindness hackathon that was the start of the Taarifa software. Nice enough, but they spent 2 whole pages on it – almost 1/3 of the total report.
  2. Focusing on Software Developers: They spend the next 2 pages of the report going into detail around Ushahidi developers and who did or didn’t commit code to github. Okay… interesting to a point, but do we really care about the standard deviation of commits per contributor
  3. Forgetting about Community Members: Remember the title of the paper? Well exactly 1.3 pages of the report, less than 1/3 of the total, was spent talking about the actual community impact. You know, if crowd-sourced location based reporting can improve public service provision? And they didn’t even answer the question!

The three complaints in the write-up are spot on for trends in ICT4D as a whole, and indicative of some of the points that grate at my nerves as well. But these are not new points, especially in the GWOB+Taarifa overlap, nor does it start discussion around how to walk the fine line between tech imperialism and community involvement; discussions I agree are lacking in the field. It’s the same opening cry against tech solutionism. Which Nate and I did a whole site and presentation about recently. However, the going-for-the-face-without-looking-at-what-you’re-going-for manifest in the writeup is even more grating. The comments later show that it’s a sensationalist take on… the sensationalism of the paper’s title. And unless we’re getting into ICT4PoMo (please dear god no) I don’t see how it’s a useful rhetoric. This is a paper taken out of its highly-specific academic context and then critiqued for not being broad enough. It’s extremely short and very targeted. Of course it’s going to focus on the tech, because of the forum for which it was written. But none of that context comes forth in this critique. And if we’re going to get into the analysis-of-the-thing-as-the-thing, then the writeup is spot on, as it missed community involvement in the critique, and completely lacks context. But I digress.

The world is huge, and wonderful, and more complicated than I could ever hope to understand. Projects and people and contexts change. That’s what gives me hope in the world – that all the things that bring me tiny rage (from gender ratios to spirals of conflict to vast wealth differences) can, and will change, over time, so long as we pitch in. I’ve said it before, I’ll say it again: you are not at fault for where the world is right now. You are, however, responsible for making it suck less.

That the world is so complex and nuanced also means one of my favorite things is meeting people who work on making the world suck less in a way or on a topic that I have no hope of fully understanding. Because how could I possibly understand every angle on the myriad challenges we face? By all of us approaching from different angles, but together, we have better chances of making those improvements. When I have qualms with how someone has approached a topic, I speak up to them about it. I try to understand where things are misunderstood (remember this exchange with Patrick?). So, thanks to the author for doing that. Yes to speaking up, but in order to instigate healthy debate, for the betterment of the whole community. Because people and projects and the world change. The github repos of social good hackathons are paved with good intentions, but healthy debate within the community is based on good faith.

So, as in back in the old day of blogger rings and LiveJournal, what shall we talk about – with an assumption of moving into action – next? The community involvement in Dar es Salaam? How the Iringa District Community Owned Water Source Organizations are really excited about these “innovations,” and how they’re taking lead on it? The work that GWOB does around gender equality in the tech and response space? Or should we discuss how to ensure niche academic papers have easy links to other components of the continuation of those projects? Any extra support and enthusiasm thrown at online annotation platforms is a boon to not only situations like these, but also to the museum and open access communities. Hooray for building knowledge together!

Updates from the Field – Taarifa in Iringa

I am utterly exhausted as I write this, but I wanted to get info out sooner rather than later. I’ll likely come back through in a few days for cleanup.

We picked back up with Taarifa in London in, amazingly, the building it was birthed out of. Note I didn’t say conceived in. It’s a project created from deep field experience, in talking to people who live in areas with lacking water infrastructure, and seeing a gap between knowledge held in a community, the knowledge those with lots of resources to wave around have, and fulfilling the need of access to water. It’s one of the few projects I’ve seen in years of hackathons that beyond building a project to feel good, and to learn more about what response is like [which I think are both worthwhile, it’s when conflated with “field-ready” that this becomes an issue]. This one has been carried forward for years, deployed in multiple countries to various success, and always at the request of (to start AND stop) of the local government[Of course my grassroots, activist self grumbles at this]. We were back at UCL, hosted by Muki’s ExCITeS group, and things just sort of worked. More reminiscent of a hackerspace or Libre hackathon than the recent industry ones[hackathonfaq.com]. Most of the team that would be in Dar es Salaam was with us for the hackathon, and we hunkered down and sussed through code – SMS, base code, email integration, and going over again (and again) the dev environment installation documentation. This wasn’t just about getting the barebones up and going, it was also about being sure we could easily onboard new people. Because next stop – back to Dar es Salaam.

In case I haven’t said it before, I’ll say it again here – the series of hackathons were to have base infrastructure in place, and to work with local software devs to maintain their own version of the code. Doesn’t make sense that it’s in the coding language it is? Let’s change it! The last thing we want to do is design, create, and implement a “solution”[man I hate that word] from far away. Because it’s not just about the tool being used well by a community – it’s also about the community fully understanding it, and having full control over the tools they use.

The hackathon in Dar ran Saturday Sunday and involved our team of 7 people – 2 grad students for general assist, 1 core code contributor, 1 cartographer, 1 person from World Bank, 1 hardware person, and myself – and another 12 local students, software developers, and entrepreneurs. [Again, one slightly angsty point for me was that we worked closely with innovation spaces, not hack spaces. Do you know about my NOLA experience? I’ll tell you about it some time. Hilarious. But I definitely try to get as close to the root as possible when working.] We worked on the SMS implementation (yay Telerivet!), backend integration, a smartphone application[many of the water engineers have smart phones – we checked. Thrice.], and the dashboards. From the funds available through the innovation grant, we hired 3 enthusiastic and competent locals to continue working not he project over the next 3 months (at least). They’ll be joining for the biweekly Taarifa call-ins[which you can also join – will be posted to the GWOB Google Plus page once I have my wits about me – but you can see all the past ones via the same place].

Unlike many hackathons, the time limit on this one wasn’t arbitrary. We (Mark from World Bank, Austin from MoMo, George and Gregor on Taarifa, an awesome local and hackathon attendee who was able to join us named Fufiji, our amazing driver Mr Wensei, and myself – sad to see Jeremy the cartographer and Andreas, our other grad student, go away) into the car at about 19:30 and headed to our stopover in Morogoro, to continue on to Irigina the next morning. 5 hours on the road, most in traffic of a supply chain made apparent, we took up half of the dark hotel we arrived at early early in the morning. Bed nets overhead, farm animal noises out the window, we slept the sleep of exhausted travel and intensive thinking. The day after, we continued at a leisurely pace to Iringa, stopping to eat fried chicken and check out hardware stores for Austin’s MoMo. We crept along mountain roads, behind cautious trucks, their brethren crashed along the roadside and pilfered for parts. I sang Flanders and Swann, Mark sang naval songs, but we generally shared silence and admired the vastness and beauty of this country. The buildings with Xs on them are within 30 meters of the road, and are slated for demolition if cities ever grow in these rural areas – a hedged bet against the traffic nightmare of Dar. Drivers signal to each other with blinkers and high beams and horns about upcoming speed traps, safety in passing, and general hello’s. And when we finally arrived, we ate chicken and fish by the light of cell phones, the power having gone out, and talked about the next couple days.

The first day we met with district officials to explain the purpose of the innovations, so we might move forward with their blessing. It’s an incredibly hierarchical society, and so authority buy-in is essential. The district water engineer, the head of health, and of education, and even the executive director of the region come by. We demoed Taarifa, and MoMo, and everyone was much impressed. But I was left feeling.. lacking. I wanted people to understand how it worked, and how it was important for their workflow (if it was). Patience, our community partner reminded me. Tomorrow we will do activities. We go back to the hotel, and Austin solders, and I draw, and we all type and talk. The gents head out to a local bar, stopping to take part in a dancing line for a music video on the way. I stay in the hotel, knowing I will only be angry about gender politics if I venture out into night life.

The second day, I lay out a game. We have 8 water points, and the room is divided up into community members, COWSOs (Community Owned Water Source Organizations), water engineers, and the district water offices. We set some constraints – the water engineers can only visit so many water points in a round, the district should know what’s going on at the end of the round so they can properly send funds. They have data in a database about what the water points were at when last surveyed, a couple years ago. Now, GO. 10 minutes to repair anything they can. Chaos. Some points get fixed, but the water engineers went to more villages than their limit allowed (we said they were flying! Not on buses. We laugh), often to places where the points were already fixed, and all in one group. Now, reconvene and talk through it. The COWSOs were completely left out (just as they are right now! Again, laughter, but there’s something deeper there, something we don’t have time for right now), and some villages were never visited. And the district gave money to places that they had listed as broken – some of which had been fixed, and didn’t give money to some places because they thought it had been fixed but it wasn’t. We talk through distribution of money – of course places with fixed points would make good use of extra funds, but they’d prefer those with less than they have get much needed funds instead.

We redefine the parameters. Anyone can send Taarifa a message (as represented by Fufuji with a spreadsheet) about their water points. The water engineers can pay as much or as little attention to it as they want, and the district can make their report off of the information, since the platform will have seen the updates to the water. We go through the exercise again, and this time there is clarity. We talk through it. Resources were better used. Time was better used. Everyone felt heard[It was, in all honesty, pretty awesome]. Then we take tea, demo the actual tools, and head out to the field.

Austin fit an exposed pipe with a MoMo, updating the firmware from the field. First time I’ve seen someone code from a pit, hands dirty, umbrella held overhead to shield the screen. We struggle with what SIM card to use in this spot, how to test given water hasn’t flown since morning, and that a 1” pipe was promised but a 3/4” pipe is what we’ve got. It finally works, tape and adapters and dirt-laden code, everyone sweaty but high on possibility. If it will send updates under the 2.5 feet of dirt which will also protect the device and the pipe from elements and scrappers, is another question. We send some messages via Taarifa, and thank everyone, and acknowledge George, Gregor, and Austin will be back within a week. Reiterate that it is the combination of the device and the people that ensure a robust system.

And then we have to get in the car and race the sun and the mountains and the supply chain on dangerous curves so I might catch my flight. An 11 hour car ride later, I’m sitting in an airport, queuing up my laptop to write this, exhausted but happy.

Taarifa Hackathon Updates

We camped out for a few lovely days at the inspiring Little Devices out of N51 at MIT. Hugs and hearts to Anna and Jose who brought their brains and their space to our hackdays. And didn’t find our requests for things like buckets, tubing, and CNC strange. We were constantly surrounded by go carts and craziness. So happy.


Mark used the OSM-Bright style and started to add Tanzanian Open Data to create a basemap for Taarifa (and generally anyone interested in Tanzania). Have started to refocus the cartography on public services as opposed to navigation – roads are the design focus of OSM Bright – Mark is changing this!

Requests have been made to import this data into OSM, however, as yet have been unsuccessful – I am following up on this! So, seeing as I can replicate OSM’s stack insofar providing a map tile service is concerned, I’ve started to create a Tanzanian base map.
Before: TZ Before


After: TZ after

Next Steps

Currently continuing to work on it. Will need to understand how the loading of OSM Stylesheets into TileMill can be re-consumed by others, currently the work is installed on a local TileMill and isn’t packagable for wider consumption. Changing this is a priority.

Lives at

On Mark’s computer – needs to be on a github repo. As a (rather large) side note. The finished product will need to be hosted on a server with at least 100gb of space, if not more. Consequently understanding where and who has this infrastructure will be important.

User Interface / Dashboard

Drew did a bunch of work on this. Here’s a drawing from brainstorming:

And a link to the PDFs.
Screen Shot 2014-05-16 at 7.24.56 AM

User Stories

It’s important to know who your users are, if you’re going to build any tool. By building out user stories based on experience and interaction, we can consider message format, connectivity, visual needs, and the like. Willow typed up a bunch of user stories based on her week in Tanzania.

Next Steps

There are some lingering questions that not enough experience was garnered in order to answer. Things like – if we want to show people that their reports are being acted on, but we can’t send them text messages back (if we’re protecting their identities), then having printouts at local municipal offices makes sense. What should those look like?

Code Base

Dirk and Florian led the charge on this.

  • Created initial installation and usage docs for the API and Waterpoints flavour of Taarifa.
    • Drew helped to guineapig this
    • range of bug fixes & doc fixes
  • Understand the sensor use case and how that relates to the Taarifa use case. Settle on the use of a separate, existing dedicated sensor api solution (potentially MITs chain-api).
  • Trying to complete the TaarifaWaterpoints application but ran into technical issues. Lots of debugging with Florian which lead to more a fundamental discussion as to what the scope of Taarifa should be.
  • Technical issues pretty much solved with a couple of things swept under the carpet for later. Scope discussion started on the mailinglist, community needs to comment (this is where a board could be useful)
  • Lots of discussions with Spencer (chain api), Jude (Promise Tracker), Ben (MoMo), Dan (Riffle) in between

Next Steps

  • Complete Waterpoint example so it’s usable
  • Main priority: focus on UI / Dashboard, implementing Drews mockups.
  • In parallel continue work (who?) on a more flexible, generic API depending on outcome of scope discussion on mailing list
  • Don’t actively evangalize Taarifa codebase to outsiders and other applications without some caveats.



Day 2 Updates

What Else?

There was also some killer work done on water sensors with Public Labs, and on telephony plugins with Tropo. Look for that followup here!

What’s Next?

Next, we’re taking this show on the road to University College London 5/24 and 25 (bit.ly/taarifalondon), and then to Dar es Salaam (bit.ly/taarifadar). We hope you’ll join us, in person or remotely, for one or both.

See the list of our tasks on this hackpad page.

Dar pt 3

Thursday is a holiday, and so no meetings – we wake up early and head to Mkuranga District – a rural, rather than urban (like Tendale), slum. We run for the ferry, tho thankfully we don’t have to jump for it, new journalist friend Erin in tow. On the other side of the sea, we drive for hours, slipping between staring out the window and talking about interactions and plans. When we finally arrive, Msilikale talks with some women about if they’d be ok to be interviewed. We negotiate money amongst ourselves – in the US and Europe, you get paid for research subject time. Here, there’s an expectation that uzungu will provide money. I offer to buy a meal or drinks1, but it doesn’t go over. Even this is complicated, with potential larger ramifications. What expectations are we setting? Are those ok? Ethical? The lacking infrastructure and predictability isn’t just about drains and tap water, it’s also about social interaction and protocols2

We talk about sewing, and water, and responsibility. There are only wells here, and those only produce salt water, with which they clean, wash, cook, and drink. There was once a community-held water point, but it broke at some point and it wasn’t fixed. The assumption is that the government will install the infrastructure, in the same breath as a complete lack of belief that it will ever happen3. Water can only be gotten when there’s electricity.4, when it can be gotten at all.

reports from the field

Again, there’s no central square, no place for known dissemination of information. Everything is done by word of mouth, neighbors talking to each other. Do they ever update each other with phones? No, there’s too much worry about the cost coming back to them (or to the person they contacted). But they’d be happy to do what’s needed to bring water to their place. If mgunzu like me try to figure out things, how can we avoid being jerks5? So long as the government brings it in, they’ll work with it. Again, this weird relationship to authority.

We hang out by one of the salt-water wells while Msilikale finds a taxi6, watching people bring carts and buckets to fill up. Children throw rocks at a lizard, chase each other, drink water from the bucket used to wash clothes now hung to dry. We stand under the gas station awning during a short but heavy rain, and then pile into a car for the long journey back to Dar es Salaam. Now it’s back to interaction at the scale of organizations, but now as informed as it can be on our short time scale by interactions with humans as humans, not in aggregate for logistics. The UNHCR refugee camp in Northwest Tanzania seems most appropriate for the water sensor innovation test deployment, as it’s a closed loop. Kibaha makes the most logistical sense for the test deployment of Taarifa, as a lot of cultural work around accountability has already been done there by a potential partner organization. Mkuranga doesn’t make sense because it’s too far out, there’s no existing social infrastructure for organizations, and there aren’t plans to put in water infrastructure for awhile yet, so people would quit reporting after awhile of no results. It’s all practical, but not cold. People here feel their responsibilities, just like anywhere else.

The next morning it’s raining as we gain a blessing from the Ministry of Water – we’ll work with their water engineers on updating reports of water points7. We sit in a taxi in traffic and talk, then meet with a potential local partner who will help with social interaction and embedding – managing expectations, closing feedback loops, continual interaction for a more successful launch – or for a better understanding of a failed launch. If it works in Kibaha, we’ll try it out in Mkuranga, with more focus on the sensors than on the reporting, to ease survey fatigue. We get back in the taxi and talk more while we head back to the Ministry of Water to talk to some engineers about what they would want out of a reporting system (yay more talking to people who use Taarifa, not just read the outputs!). As the depth of the water on the road increases, the speed of the traffic decreases. Finally, concerned about even making his flight, we send Mark off in the taxi with his luggage, and I pile into a bajaj with my own suitcase. A meeting to get to, and facilitate, on my own!

Everything goes beautifully. I’ve learned to hold firm when I’m told someone doesn’t have time, or tells me they only have a few minutes. “We’ll talk again on Monday, but right now I do want 15 minutes. That’s it.” Engineer B and I end up sharing frustrations, drawing on pieces of paper, and giving a firm handshake at the end. Msilikale and I meet up, and head to my new lodging – not the fancy hotel anymore, but a friend’s-of-a-friend house. From here, I can still see birds flocking, and the sun setting over the sea, but there are also bugs and the shower is weird and it feels so much more comfortable than the fanciness. We have dinner with one of her Dutch friends, and brave traffic, and bond over growing up in the Midwest. The ensuing days are similar, with one day blissfully off. Plans for Zanzabar are trumped by epic, amazing rains. I read frivolous articles on my iPad and watch the rain roll over the sea.

In all this, the World Bank8’s hammer is money, and so everything looks like a project to fund. What makes this a complicated mess to my anti-capitalistic heart is that, indeed, many projects do need funding in the current environment. I see the “we read as much about about a grassroots thing that works as we could, and this is how we think we should do it…” All the people I’ve met within the org want a way to make the world to suck less. But these are institutions whose tools are people, and funding, and other institutions. And while they try various tactics, and sometimes make headway, in making the world suck less… they’re also held accountable for their actionsIn theory.. The difference is, the people in grassroots initiatives have to live with the reality of the failings and successes of their (and institutional) endeavors. So of course they are who I think of first. And last. And always9.

And Msilikale and I go over the drawings I did, and listen to music, and talk about all sorts of things. The power goes out, and we keep talking, the windows closed against mosquitos and the oppressiveness of the growing heat inside overwhelming. We walk in the dark to a local Indian joint, eating overly peppered food and listening to the calls to prayer out the window. The lights go out there, too, and we eat by the light of cell phones until the generators kick in. “This,” say Msilikale, “is Dar es Salaam.”

1. Worked for Kibera.
2. Scott’s Seeing Like a State is ideologically interesting, but if there’s no way to get clean water but through organized distribution of resources, such ideology gets tempered at least a bit.
3. It’s like breaking up with someone before they break up with you.
4. Mind you, this is a project with the Ministry of Water. Not Ministry of Power. This is with water. So we can only focus on water. *shakes fist at silos*.
5. Again, Msilikale mitigating anything that seems like a promise. Or hope, really.
6. Easier to negotiate price if we’re not there.
7. The hand washing tap in the MoW does not in fact produce water. Oh, the irony.
8. A World Bank innovation fund is what is supporting this initiative.
9. Not saying others don’t, simply that there sure does seem to be a lot of reminding.