Skip to Content

The Lessons of Aaron Swartz

With technology comes power. Shouldn’t MIT teach students how to use it responsibly?
October 4, 2013

On the day after Aaron Swartz’s death in January, President Reif and I spoke about how MIT might respond to the breaking news of his suicide. A well-known Internet activist and advocate for democratic principles and open access, Swartz, 26, had made important technical contributions to the Web’s architecture at age 14. For his last two years, he had been the subject of a vigorous federal prosecution by the Boston U.S. attorney on charges of using a laptop connected to the MIT network to download millions of research journal articles from JSTOR, a digital library of academic journals, books, and primary sources. The president wanted MIT to publish a full report about our involvement in Swartz’s arrest and prosecution. Others urged against that: there was already tremendous anxiety among MIT employees who had been involved, and an investigation could make matters worse. Even on that first day, criticism of MIT was already surfacing on the Internet: an investigation and report could bring increased exposure and risk to the Institute and its people. Wouldn’t it be more prudent to remain silent and let the storm blow over?

Hal Abelson
Hal Abelson

The arguments for openness prevailed, and the next day the president asked me to take on the task of creating a report. The charge was to produce an objective public record that people both inside and outside MIT could use in drawing their own conclusions about MIT’s actions.

Creating that record took six months, and I had the great luck to work on it with Institute Professor emeritus Peter Diamond, assistant provost Doug Pfeif­fer, and computer law attorney Andy Grosso. We interviewed 50 people, reviewed 10,000 pages of documents, and in July published a 180-page report that answers the question of “what happened.”

Determining what happened is only part of MIT’s response. In my first talk with President Reif, we agreed that the key purpose of producing a report was to help MIT to learn from the tragedy. For the president, this was to be a two-part process. Publishing the report was part one.

MIT is now at the second part of the process. What will our community make of what happened, and what will we do as a result? While many people have told me they appreciate the report’s clarity and detail, others have expressed skepticism that MIT will really address the eight key questions it raised. We’ll see over the coming months what lessons the MIT community takes to heart.

Some lessons are straightforward. The report identifies gaps in our policies for handling digital information, and confusion about procedures. Beyond that, we need to review our practices for inviting outside law enforcement to campus—particularly for technology-related crimes, where calling the local police can be tantamount to bringing in federal agents, as happened with Aaron Swartz.

Other questions address our values. In reviewing the record for the report, I was struck by how little attention the MIT community paid to the Swartz case, at least before the suicide. The Tech carried regular news items on the arrest and the court proceedings. Yet in the two years of the prosecution, there was not one opinion piece, and not one letter to the editor. The Aaron Swartz case offers a textbook example of the issues of openness and intellectual property on the Internet—the kinds of issues for which people traditionally look to MIT for intellectual leadership. But when those issues erupted in our midst, we didn’t recognize them, and we were not intellectually engaged. Why not?

For me, the most vital questions that arise from the report have to do with our responsibility as educators in an age of technology. Though Aaron Swartz was not an MIT student, he was like many of our students: brilliant, passionate, technically empowered. Yet he was also dangerously naïve about the reality of exercising that power, to the extent that he destroyed himself. We might well ask whether the people who mentored Swartz and helped him achieve such brilliance and power had a responsibility to cultivate not only his technical excellence and his passion as an advocate but also, as my grandmother would have called it, seykhel—a wonderful Yiddish word that means a combination of intelligence and common sense.

We can ask the same thing about ourselves. The young people we work with are so extraordinary, and are so empowered by their time here; do we at MIT have a responsibility to help them grapple with the reality of that power? And in a world where technology brings power as never before, can we remain leaders in education if we don’t meet that responsibility?

Hal Abelson, PhD ‘73, a professor of electrical engineering and computer science, chaired the review panel that analyzed MIT’s involvement in the Aaron Swartz case.

Keep Reading

Most Popular

This new data poisoning tool lets artists fight back against generative AI

The tool, called Nightshade, messes up training data in ways that could cause serious damage to image-generating AI models. 

Rogue superintelligence and merging with machines: Inside the mind of OpenAI’s chief scientist

An exclusive conversation with Ilya Sutskever on his fears for the future of AI and why they’ve made him change the focus of his life’s work.

The Biggest Questions: What is death?

New neuroscience is challenging our understanding of the dying process—bringing opportunities for the living.

Data analytics reveal real business value

Sophisticated analytics tools mine insights from data, optimizing operational processes across the enterprise.

Stay connected

Illustration by Rose Wong

Get the latest updates from
MIT Technology Review

Discover special offers, top stories, upcoming events, and more.

Thank you for submitting your email!

Explore more newsletters

It looks like something went wrong.

We’re having trouble saving your preferences. Try refreshing this page and updating them one more time. If you continue to get this message, reach out to us at with a list of newsletters you’d like to receive.