**This is an old revision of the document!**

Hacker Culture and Politics

What is this course about?

We are all hackers now. This course chronicles the story of a kind of identity that began among a geeky subculture, then migrated to a murky criminal underground, only to be adopted by management consultants and CEOs. Do hacker formations like Wikileaks, Anonymous, and open-source software represent a new kind of politics, or a rejection of politics as we know it? We will explore the contested figure of the hacker in the past, present, and science-fiction of the Internet.

Since anyone who has signed up for a course with this name can probably expect to be on some watchlist for all eternity, we'll also have to learn skills. Expect to teach yourself and one another something technical. Hacker politics is not a spectator sport.

What are the expectations?

Basically, students are expected to hack it. This can take different forms for different people. We'll work together to make the expectations clear, and then it's up to you how and to what degree you'd like to meet them.

Objective 0: Contribute

Student are expected to attend scheduled meetings and contribute to the class community. Each week, we'll follow a similar pattern:

  • The first day, we'll learn a skill from a member of the class and hack on it together. On hacking days, it's a good idea to bring a computer with you.
  • The second day, we'll discuss the readings for the week in light of our experience hacking. Screen devices allowed only for referring to the readings. Notes must be taken on paper.

Online, the course lives on a private GitLab repository, accessible only to members of the class.

Objective 1: Hack

Before every week's second class period, each student should post an “exploit” on the week's GitLab issue. This is a brief blog post detailing something you did with the week's skill, discussed in interaction with the week's texts. It need only be long enough to demonstrate some adventuresome thinking.

Objective 2: Teach

We learn from each other. At some point in the course, each student will present to the class a hacker skill that they have learned. One skill per student—you'll sign up ahead of time for a skill and a day to present. In a 10-15 minute presentation, including slides and/or a live demo, share with us not only the skill but the learning process you went through to obtain it. In advance of the presentation, you will also be expected to outline your presentation on the class's GitLab wiki, which classmates may edit and amend.

Objective 3: Reverse-engineer

Become a goon. The final project for this course is to write an approximately 1,800-to-2,000-word report on a real-world hack for a relevant establishmentarian organization. If the hack in question is of questionable legality, write as an FBI agent, perhaps. If the hack is just a brilliant piece of technology, write as a stiff for a big computer company trying to figure out how to capitalize on it. In any case, with clear language and documented research, explain the nature of the hack, its significance, and a recommendation for what your organization should do about it.

This project includes a built-in debugging and revision process.

Bounties

Grades are not especially conducive to hacking, but we need some equivalent in order for this course to be legible to the university. Therefore, work will be rewarded with bounties. These are functionally pretty much the same as grades, but perhaps giving them a different name will prevent them from killing the learning process in the way that grades normally do. The maximum bounty awarded for each portion of the course is as follows:

  • Objective 0: 20 points
    • attendance; only absences with documentation from a relevant authority will be excused; more than 3 unexcused absences will result in a loss of 2 points each
    • thoughtful contributions to the discussion that demonstrate grasp of the readings
    • evidence of attention to others
    • good questions
    • active collaboration in learning and sharing skills
  • Objective 1: 30 points
    • clever use of the week's skill
    • sophisticated engagement with the texts
    • punctuality
  • Objective 2: 20 points
    • demonstrated autodidacticism (with appropriate community help)
    • ambition of the skill, balanced with realistic expectations
    • background information on the history and rationale of the task
    • accessibility and fun of the presentation
    • usable contribution to the wiki
  • Objective 3: 30 points
    • complete beta version:
      • 1,800-to-2,000-word length
      • comprehension of the hack and accessible analysis of it
      • appropriate references to at least three assigned readings
      • impressive and documented research
      • correct grammar, correct spelling, coherence
    • participation in debugging
    • evidence of revision for final

Bounties will be compiled in real time on D2L for easy access. The final grade will be calculated by adding up the bounties each student has earned.

Terms and conditions

  • When problems arise, we will seek to address them collaboratively—first through dialogue, then through revision of this document, and only if those are inadequate through recourse to outside authorities.
  • We respect one another's privacy. Content shared in the course will not be shared beyond it.
  • Use of laptops and other screen devices is discouraged during class time. They are highly likely to interfere with your learning experience. Most class activities, unless otherwise stated, neither require or will be improved by them.
  • We adhere to basic university policies regarding accessibility and academic integrity; we take responsibility for understanding them and the relevant procedures. Verbum sat sapienti est.

What topics will be covered?

Whois?

Skill: Hack something.

School

Skill: Teach yourself something.

Craft

Skill: Write a command-line script.

Sharing

Skill: Set a valuable piece of information free.

Law

Hacking IP:

Hacking corporate structure:

Skill: Devise a license.

Order

Gittip/Gratipay, the firstsecond “open company”:

Skill: Submit a bug report or feature request to an open-source project.

Security

Skill: Encrypt a form of digital communication.

Culture

Skill: Make a remix.

Anonymity

Another use of anonymity and geopolitics:

Skill: Create a robust pseudonym.

Power

Skill: Social-engineer something.

Money

Skill: Get some bitcoins.

Gentrification

Skill: Co-opt something.

Wiki

What remains to be read? We'll decide together as a class.

Skill: What remains to be learned?

Reverse-engineering

Peer review the final project and conclude the course.


What should I be checking out to keep up with hacker culture?

To whom is credit due for the composition of this class?

Quite a bit of the material came from this course with the same name offered by Gabriella Coleman. Read my profile of her here.


[ Notes ]