Related:

• ARMM n. [acronym, `Automated Retroactive Minimal Moderation'] A Usenet cancelbot created by Dick Depew of Munroe Falls, Ohio.
  ARMM was intended to automatically cancel posts from anonymous-posting sites....
• Dave the Resurrector n. [Usenet; also abbreviated DtR] A cancelbot that cancels cancels.
  Dave the Resurrector originated when some spam-spewers decided to try to impede spam-fighting by wholesale cancellation of anti-spam coordination messages in the news....
• Breidbart Index /bri:d'bart ind*ks/ A measurement of the severity of spam invented by long-time hacker Seth Breidbart, used for programming cancelbots.
  The Breidbart Index takes into account the fact that excessive multi-posting EMP is worse than excessive cross-posting ECP....
• despew /d*-spyoo'/ v. [Usenet] To automatically generate a large amount of garbage to the net, esp.
  from an automated posting program gone wild. See ARMM....
• cancelbot /kan'sel-bot/ [Usenet: compound, cancel + robot] 1.
  Mythically, a robocanceller 2. In reality, most cancelbots are manually operated by being fed lists of spam message IDs....
• despew: /d*-spyoo'/ [USENET] v. To automatically generate a large amount of garbage to the net, esp.
  from an automated posting program gone wild. See {ARMM}. -- The AI Hackers Dictionary...
• pam vt.,vi.,n. [from "Monty Python's Flying Circus"] 1.
  To crash a program by overrunning a fixed-size buffer with excessively large input data....
• aliasing bug n. A class of subtle programming errors that can arise in code that does dynamic allocation, esp.
  via malloc(3) or equivalent. If several pointers address (`aliases for') a given hunk of storage, it may happen that the storage is freed or reallocated (and thus moved) through one alias and then referenced through another, which may lead to subtle (and possibly intermittent) lossage depending on the state and the allocation history of the malloc arena....
• aliasing bug: n. A class of subtle programming errors that can arise in code that does dynamic allocation, esp.
  via `malloc(3)' or equivalent. If several pointers address (`aliases for') a given hunk of storage, it may happen that the storage is freed or reallocated (and thus moved) through one alias and then referenced through another, which may lead to subtle (and possibly intermittent) lossage depending on the state and the allocation history of the malloc {arena}....