Theorizing the Web abstract

Discourse on hackathons tends to emphasize projects and project creators rather than the events as a social practice within existing communities. Hackathons have a history as a community building method for education and creation. More recently, institutions have used hackathons to invite conversation and design with groups affected by those institutions. This step towards broader participation is obfuscated by stories that focus on the creation of products and the lucky geniuses whose work is appropriated by institutions. Critiques of hackathons often accept the same assumptions, focusing on high profile events, critiquing the small number of sustained projects, and questioning hackathons as a form of entrepreneurial free labor.

We argue that hackathons are a community practice which is poorly expressed by this focus on project outcomes. Based on our historical research and interviews with hackathon organizers, we show evidence for ongoing contributions to community objectives as a core value to many events. Hackathons have been a community practice for decades in open source groups, hackerspaces, and companies. People participate to learn, signal their belonging to the group, and at times to make something new. Many communities hold regular hackathons as one component of their larger initiatives.

As hackathons have become more popular, governments and companies without a history of engaging with people outside their organization have been using them to listen to critiques and to support people and ideas that they formerly lacked the capacity to hear. Hackathons are offering a new channel through which marginalized groups can remix, critique, and relate directly to people within those institutions. However, project-oriented narratives about hackathons motivate institutions towards easy, shallow, visible innovation from people who already know the institution. The visible project and its creators, rather than communities or process, are the goal of these hackathons, which reinforce the status quo. Repeatedly failing to meet expectations can inoculate institutions and participants alike from further engagement. Project oriented narratives also limit hackathon’s ability to share community values with new groups, encouraging and rewarding individualism rather than the more historically-common practices towards education and expanding sustainable projects.

In this talk, we illustrate what’s missed by project-oriented narratives via interviews with hackathon organizers and a series of case studies. We will also offer examples of alternative discourse that highlights community practices, learning outcomes, and critical discourse that occurs within hackathons.

Theorizing the Web Talk

Nate and Willow’s talk at Theorizing the Web 2014 on Hackathons are More than Hacks starts at 50:12

  1. Set up the mismatch between media and practice (3 mins max
    1. Introduce ourselves
      1. Willow
      2. Nathan
    2. N: If you’ve read about hackathons in the press, you’ve probably seen
      1. clever young hackers winning prizes for making tech
      2. rather than a community of all ages learning together
    3. W: show a quote by an organiser
    4. W: and a quote from a participant
    5. N: In this presentation, we share some early results from research on hackathons. We’re seeing a mismatch between media narratives and the stories participants themselves tell, a mismatch that is colouring critiques of hackathons.
    6. (describe our methods and context) (45 seconds) (brief)
      1. w: what is a hackathon, based on our experience and our interviews
      2. w: we interviewed around 15 participants, organizers, and facilitators.
      3. n: we analysed around 640 articles and blog posts about hackathons
      4. w: we’re involved
  2. W: In my interviews: Hackathons at the intersection of community building and engagement with institutions (who are the players, and what are their goals) (2 min)
    1. What hackathons we’ve looked and been involved in
      1. (slide) with a big list of logos and what years are covered with us and the people we’ve talked to
      2. (zoom) Communities (slide with lots of examples) (open source, disaster response, entreprenuers)
      3. (zoom) Organisations (slide with lots of examples) (businesses, governments, non profits)
    2. Who attends (front end, back end, subject matter experts, students) or just (do this for THEIR LIVING, professionals who want to volunteer their tech skills on a weekend, folk who want to learn more about a subject, folk who are passionate about a subject but don’t know how to engage)
  3. W: What actually happens at and after hackathons (3 mins) include a bunch of quotes
    1. People learn about new disciplines and challenges
    2. People find a way their skills can change the environment they’re in
    3. People find others with shared interests
    4. What happens with projects & initiatives
  4. N: How hackathons get portrayed (2 mins)
    1. Slide of what media we analyzed, including list of sources, MediaCloud mention, and histograms for Hackathon and Civic Hacking (640 articles)
    2. Simple revolutionary solutions
    3. Civic Hacking (80 articles & blog posts)
      1. equal measure PR
      2. project documentation
      3. critiques of the idea
    4. Superstars & Startups
    5. last point: mismatch between media narratives and interview results
  5. Major critiques of hackathons – coming from theorists, critics, and funders
    1. slide that points to hackathon critique articles & minisites (don’t try to respond)
      1. example: MELISSA GREGG & CARL DISALVO “The Trouble with White Hats” (New Enquiry) (http://thenewinquiry.com/essays/the-trouble-with-white-hats/)
      2. example: National Day of Hacking Assumptions & Entitlement (http://nationaldayofhacking.info/) voices from people in those communities. Disconnect causing animosity.
      3. Morozov “Making It” New Yorker: http://www.newyorker.com/arts/critics/atlarge/2014/01/13/140113crat_atlarge_morozov?currentPage=all
      4. David Sasaki (Omidyar, now Gates Foundation): On Hackathons & Solutionism http://davidsasaki.name/2012/12/on-hackathons-and-solutionism/
    2. List Critiques (willow)
      1. Produces incomplete & short-lived projects (prototyping) – addressed when about the community rather than about the media.
      2. Free labor for companies & gov’t
      3. Doesn’t create fundamental change
      4. Props up existing structures, making them more efficient
      5. Inauthentic citizenship as alternative to meaningful change
      6. Only addresses technically actionable solutions
      7. It’s impossible for tech to support meaningful structural change
      8. False Empowerment: Solutionism in a weekend
      9. Distraction: People feel good about shiny ideas that never have impact
      10. Emphasizes superstars rather than communities
      11. Entrenches exclusion by favoring people with technical skills
    3. Nathan: What ties these critiques together is an emphasis on media portrayals and less a focus on actual community practices we’re seeing
      1. Media doesn’t emphasize learning
      2. Media doesn’t emphasize community building
      3. Media supports an overly simplistic solutionist narrative
      4. Media prefers a one hero story about shallow revolution
      5. Media attention focused around the hackathon event, with limited follow-up: if projects proceed beyond prototype, we don’t hear about on going effort
      6. All of these things can obscure what really happens
  6. W: Based on what we’ve found: Responsibility for hackathons, media, and researchers, for a method that’s still growing and evolving (3 minutes)
    1. W: Impart a sense of what these become as what we make of them. By their very nature, they are malleable. People with skin in the game need to be engaged with responsibly.
    2. W: Solid as a working method – especially cross-culturally (closing technological gaps as well as socioeconomic / access gaps)
    3. W: So you’re organizing a hackathon – think about how you’re portraying it to all parties, and make sure to amplify communities and practices, not just projects
    4. M: So you’re reporting on a hackathon – reporting on projects is lazy – look deeper into the community practices, learning, and engagement with institutions
    5. M: So you’re researching hacker culture – find a stance that acknowledges and respects the voices, experiences, and work of the communities whose outcomes and potential will be directly affected by the arguments you make from a position of power and privilege. Go beyond critique and simple media criticism for a deeper engagement with communities and practices
    6. W: Use & contribute to hackathonFAQ.com

Parameters of Social Interaction

What does equality look like? How do we know if we are getting there?

This is the question I asked to open my talk at SHA 2017. It is also the question carried with me as I walked into CtK.Campfire. Both aimed to look at how to mitigate the polarization of human interaction in a digital age. The talk looked at the infrastructure of human interaction, and the retreat embodied some of the best ideals towards action. I’ve written two blog posts – one about each event – but they occurred temporally and intellectually adjacent. You can find the post about CtK.Campfire here.

The talk at SHA2017 (the Dutch hacker camp) was called “Weaponized Social.” WeapSoc is a project in which Meredith and I invested heavily through 2014 and 2015. She has gone on to write for Status451 on an extension of the topic area. I’ve continued to frame bits of my work in this context but have generally not kept up. It’s some of the most intellectually stimulating and emotionally draining work I’ve ever done, and that includes disaster response in the field.

A background assumption for this talk is that the effects of violence become less and less apparent to an observer of a single instance as we push the edges of “acceptable behavior” into being more aligned with human rights.

Violence is defined by the World Health Organization as “the intentional use of physical force or power, threatened or actual, against oneself, another person, or against a group or community, which either results in or has a high likelihood of resulting in injury, death, psychological harm, maldevelopment, or deprivation”, although the group acknowledges that the inclusion of “the use of power” in its definition expands on the conventional understanding of the word.

Example: seeing one person hit a non-consenting person is (pretty) easily defined as violence. Seeing one person say “your a dumb bitch” online to another non-consenting person isn’t as easily defined as violence (it’s often instead categorized as “conflict“). We have to zoom out to see that the receiver isn’t able to be online any longer due to thousands of similar messages in order to see it as the violence (in the form of depravation to opportunity or psychological harm) it is. Here’s just one example:


I don’t want to limit what this person says, but I also have a right not to experience him saying it, if it detracts from my ability to be online. As the quote says, “your right to swing your fist ends where my nose begins.” How can we bridge this sort of contention at scale?

To zoom out like this, and to take action at a systemic level, we luckily have Lessig’s four forces for social change. As the infosec crew which was the audience at SHA is largely skeptical of law (excepting the EFF), of social norms (“don’t tell me how to act”), and that I’m skeptical of markets being able to solve problems of inequality, we are left with architecture/code.

In the talk, I asked this question:

“Do we want to take a scientific approach to equality, where we tweak our infrastructure in explicit ways to see if it changes how people are interacting?”

We, as the creators and maintainers of online spaces have a responsibility to strive towards equality in the ways available to us. How can we do this without surveillance and control of speech? We change the architecture of the spaces. The crew of Weaponized Social (namely, TQ at the SF event in May 2015) started to lay out what the different parameters of social interaction are. Such as, how many people can one account be connected to, how far a message can travel (through timeouts or limits to re-broadcasts), of if an element of serendipity is introduced. These are toggles which can be changed, sliders which can be moved.

If we change these things, we can see how/if architecture changes the way we interact. The social sciences point to us being deeply (tho not solely) affected by our environments. By changing the architecture of online spaces, we could see how it changes how we interact. Who feels safe to speak by taking part in the act of speaking. We can then make better choices about our individual instances and realities based on those results. We now have one more set of tools by which to examine if we are progressing towards equality, without impinging on the individual right to speak. I hope you make use of these tools.

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.