I wish Dr. M had made us do a geekiness. (Although I can't complain too much; writing a stats paper on the World Series isn't that bad either).

Also, I love watching geeks talk. Behold:

user1: http://en.wikipedia.org/wiki/Special:Search?go=Go&search=Snark_(punctuation) >> user2
user2: bash: user2: Permission denied
user1: sudo http://en.wikipedia.org/wiki/Special:Search?go=Go&search=Snark_(punctuation) >> user2

Now, I know my parents (who are reading this) probably don't understand why this is so amusing, and why I adore hanging out with people who can talk like that. The analogy for them is that it's like getting back to Manila - although they speak fluent English and have lived in the US for years, it's probably really nice to get back to a land where everyone speaks their creole of Min-nan, English, Tagalog, and... whatever else is in there. It's not that you can't live without speaking that language with somebody else, but there are some thoughts and patterns you can't express in any other way, and it's great to be able to get them out.

I'll do my best to explain what it means so mom and dad can see how much information (and humor, and implicit culture) is packed into the three lines up there. For any hackers out there; please correct my misinterpretations. For any social scientists out there: likewise on my methodology.

Analysis:

For the uninitiated, this is an IRC transcript; it's 3 lines from a chatroom in which two people (user1 and user2, both young men working in the software field) were talking. They know each other and are trading friendly jabs (a common way of showing friendship among... well, I'm tempted to say hackers, but I really think this generalizes to a broader social group - maybe 'guys,' or less colloquially 'western young-adult males.') The straight translation into English would go something like this.

user1: I insult user2!
user2: I block your insult!
user1: I counter-insult and succeed!

Not particularly funny, though. Let's take a look at how they insulted each other so we can see where the witticism comes in. One line at a time.

user1: http://en.wikipedia.org/wiki/Special:Search?go=Go&search=Snark_(punctuation) >> user2

Okay. First lesson: Wikipedia, a popular online encyclopedia that's user-editable and well-known among the geek set (and increasingly in non-geek sets as well). The URL provided is the "snark" article, where a snark is "A sarcasm mark or sarcasm point [which] identifies text as being derogatory or ironic." (Wikipedia)

Next, the double right angle brackets. ">>" is something used on the Unix command line to transfer information from one process (or location) to another. For instance, the command echo foo >> foo.txt will take the output of 'echo foo' (which is the text 'foo') and save it to the file 'foo.txt.' (Foo itself is a metasyntactic variable that programmers use as temporary/example variables when they can't think of any other name; I am myself a hacker and often conform to many of their communication conventions.) In other words, a >> b means "place a's output at b." I think of it as "throw at," or "place towards." So we could also deconstruct the line above like this:

user1: [oblique reference to derogatory sarcasm] placed-towards user2
or...
user1: *throws sarcastic insult towards user2*

Next, user2 replies. He's not going to take this sitting down.

user2: bash: user2: Permission denied

This is a made-up output in response to user1's insult - user2 is acting as if he is a computer that user1's command has just been called on. Bash is a shell - a command-line interface that commands (which is what user1's message is formatted to emulate) are typed into. This message is essentially saying that user1 does not have the necessary (technological/security) privileges ("privs") to carry out the insult-operation defined above - that is, to save the snark file output to location "user1." Some translations of user2's line might go like this:

user2: you can't touch me.
user2: you don't have the power to actually insult me in that way.
user2: missed me! nyah!

Finally, user1 counter-jabs with a response that bypasses the "block" that user2's comment made against the original insult.

user1: sudo http://en.wikipedia.org/wiki/Special:Search?go=Go&search=Snark_(punctuation) >> user2

Sudo means "superuser do," with superuser being the administrative account that can do basically anything on a computer (including bypassing local "Permission denied" errors). The rest of the comment is identical to user1's first insult.

If user2's comment means "you can't touch me," user1's riposte means "oh yes I can." The use of "sudo" indicates elevated access privileges and possibly by extension technical superiority, as administrative access on machines is typically only given to experienced and trusted people. The conversation thread of insults terminated here and user1 and user2 (and others) went on to discuss other things.

It is important to realize that these were not actual commands. By this I mean the comments were written with many elements of code (and would for the most part* be executable on an actual command-line) but are not purely so - they're mixed in a peculiar creole of code, colloquial English, and "hacker slang" (which includes specialized terminology). They're also typed into a chat window where they clearly won't be executed as 'actual' commands on a computer - the intent is to "run the program" on the other person's brain in order to communicate. (Which is, in one way of looking at it, what all languages... do. They're brain-executable programs and protocols in some sense.)

Recap: There are also some things exhibited nicely here that are common in hacker culture in general.

  • extended sprints of wit - subtle humor/puns and wordplay, done straight-faced for long conversations that get increasingly more humorous by building atop of twisted logic.
  • insults as a signal of familiarity and friendship - the more you know someone, the worse names you can call them as terms of endearment.
  • strong "insider" computing metaphor knowledge - this entails two things: (1) implicit understanding/assumption that the other person knows the meaning of these specialized technical commands, another insider-bonding action and (2) acceptance of mixing these computing terms with colloquial English.

*Postscript: As I mentioned earlier, I am myself a hacker. I can't (okay, "don't want to") resist adding that the command that user1 typed is invalid as presented - attempting to pipe a URL ("webpage address") directly to a file will give you the error 'bash: http://url-you-typed.com: No such file or directory' and what you actually want is to pipe the content of the page at that url to the file. (In other words, get the webpage that's at http://url-you-typed.com and [dump the text you would see in a browser] to [a file]). Therefore, I say...

mchua: links -dump http://en.wikipedia.org/wiki/Pwn >> user1anduser2

And there you go.