Related:

• burble: [from Lewis Carroll's "Jabberwocky"] v. Like {flame}, but connotes that the source is truly clueless and ineffectual (mere flamers can be competent).
  A term of deep contempt. "There's some guy on the phone burbling about how he got a DISK FULL error and it's all our comm software's fault....
• oll v.,n. 1. [From the Usenet group alt.folklore.
  urban] To utter a posting on Usenet designed to attract predictable responses or flame...
• kit: [USENET; poss. fr. DEC slang for a full software distribution, as opposed to a patch or upgrade] n.
  A source software distribution that has been packaged in such a way that it can (theoretically) be unpacked and installed according to a series of steps using only standard UNIX tools, and entirely documented by some reasonable chain of references from the top-level {README file}....
• There must be some mistake," he said, "are you not a greater computer than the Milliard Gargantubrain which can count all the atoms in a star in a millisecond?
  "The Milliard Gargantubrain?" said Deep Thought with unconcealed contempt....
• barf /barf/ n.,v. [common; from mainstream slang meaning `vomit'] 1.
  interj. Term of disgust. This is the closest hackish equivalent of the Valspeak "gag me with a spoon"....
• README file n. Hacker's-eye introduction traditionally included in the top-level directory of a Unix source distributio
  containing a pointer to more detailed documentation, credits, miscellaneous revision history, notes, etc....
• boot v.,n. [techspeak; from `by one's bootstraps'] To load and initialize the operating system on a machine.
  This usage is no longer jargon (having passed into techspeak) but has given rise to some derivatives that are still jargon....
• kit n. [Usenet; poss. fr. DEC slang for a full software distributio
  as opposed to a patch or upgrade] A source software distribution that has been packaged in such a way that it can (theoretically) be unpacked and installed according to a series of steps using only standard Unix tools, and entirely documented by some reasonable chain of references from the top-level README file....