It seems like he was accessing the MIT network simply to get an MIT IP address that would authorize him in the JSTOR application. He then was running a scraper, which was probably just a python script with a bit of metering to avoid slamming them too hard. Does anyone know if that's correct, that if your organization has a site license you can access the service without additional credentials?
If that's all true then the description of the events and charges seem to reflect quite a polarized view. It's somewhat understandable, though, that JSTOR would want to "throw the book at him" given his previous public comments - it seems very likely he intended to distribute the large cache of documents widely. Whether or not that's ethical, it's clearly not in the firm's best interests - I doubt a similar situation without any intent to distribute would be referred to law enforcement at all.
I'm not specifically familiar with JSTOR or MIT's network, but I am familiar with other services that allow free access from anyone coming via a school's network block, and I'm also familiar with networks that will allow guest access for a short period of time so as to not inconvenience true guests.
Lots of services do this because it's far less hassle than distributing traditional credentials and typically it's less likely to be abused because unlike name/password pairs, you can't post an IP address to usenet and have somebody else use it. The abuser also has to be physically present, which makes them much easier to find.
depends... what's the total value of what he stole? say, for arguments sake, it was in the 7 figure range. If I steal a million bucks from you, how long would you like me to spend in prison?
This is not the first time he has done something like this if memory serves me. In late 2008 Mr. Swartz and Carl Malamud went to select libraries, ones with free PACER access, and proceeded to download ~700 GB of information that was behind a paywall. After which they made all of it available on Mr. Malamud's website.
> Aaron's not wrong to call himself one of the founders. The company behind Reddit was a merger of two startups, one that made Reddit and one that made Infogami, and in that situation the founders of both startups are considered founders of the combined company.
He went to europe while they were in the middle of crunch time, then promptly took a week of sick time upon his return. They fired him shortly thereafter. Steve talks about it here:
In Aaron's words: "Yeah. I was unhappy working in an office and didn’t hide it. So I’d come in late and set up lots of off-site meetings and stuff. And my boss wasn’t really thrilled about that. Also, I think he was upset about me disappearing for so long on vacation. One of the places I went to in Europe was the Chaos Computer Conference. And while I was there I hung out with my friend Quinn Norton, who was reporting on the event for Wired. She took my photo for one of her articles and it was featured on wired.com’s front page. “Heh,” I joked. “I bet the first time my boss finds out where I am is when he sees my photo on the front page of his own website.”"
So yeah, he earned his firing and the emnity of his coworkers the old-fashioned way.
Edit: Also, there's some speculation on the thread I linked to that Aaron was a cofounder who received a payout in the CN deal. He wrote web.py, sure, but if he walked away with $1MM+ without showing up to work, that could explain why they still hate his guts.
I know nothing of the internal arrangements and disputes. But knowing how these things often go, it's easy to imagine that Aaron was tangentially involved, and the Reddit team needed more help, but Aaron still had another project, where his 'founding' stake/claim was larger.
Offering a founder-ish stake and founder-ish title for bringing that other project in-house (even if the combined team pursues something else) is a common resolution to such a situation.
And further: 'founder'/'cofounder' are not technically-rigorous terms, but a matter of common agreement. Followers of the iterative/lean approach should recognize that 'founding' is not a point event, at a single moment (of inspiration, document-signing, code-commit, whatever), but rather a process that continues.
Any team that adds a new key person early could reasonably consider that person another 'founder'/'co-founder'/'founding employee'. Consider all the 'looking for co-founder' posts, from people who've already made some progress.
He gave a talk at my university advocating people to release journal articles they have access to as students to the Internet.
The whole thing was very strange, as he was claiming to be a cofounder of a well known company he was not a cofounder of and he was openly advocating illegal activity.
that's unreal. Min 29 on seems to be where the direct discussion of "rule" breaking begins. Rule breaking by Swartz being getting the JSTOR files from students and placing them online.
his website mentions him as a co-founder
"...He also cofounded the online news site Reddit, where he released as free software the web framework he developed, web.py..."
If that's all true then the description of the events and charges seem to reflect quite a polarized view. It's somewhat understandable, though, that JSTOR would want to "throw the book at him" given his previous public comments - it seems very likely he intended to distribute the large cache of documents widely. Whether or not that's ethical, it's clearly not in the firm's best interests - I doubt a similar situation without any intent to distribute would be referred to law enforcement at all.