Slashdot Mirror

Everyone knows about BSD's failure and imminent demise. As we pore over the history of BSD, we'll uncover a story of fatal mistakes, poor priorities, and personal rivalry, and we'll learn what mistakes to avoid so as to save Linux from a similarly grisly fate.

Let's not be overly morbid and give BSD credit for its early successes. In the 1970s, Ken Thompson and Bill Joy both made significant contributions to the computing world on the BSD platform. In the 80s, DARPA saw BSD as the premiere open platform, and, after initial successes with the 4.1BSD product, gave the BSD company a 2 year contract.

These early triumphs would soon be forgotten in a series of internal conflicts that would mar BSD's progress. In 1992, AT&T filed suit against Berkeley Software, claiming that proprietary code agreements had been haphazardly violated. In the same year, BSD filed countersuit, reciprocating bad intentions and fueling internal rivalry. While AT&T and Berkeley Software lawyers battled in court, lead developers of various BSD distributions quarreled on Usenet. In 1995, Theo de Raadt, one of the founders of the NetBSD project, formed his own rival distribution, OpenBSD, as the result of a quarrel that he documents on his website. Mr. de Raadt's stubborn arrogance was later seen in his clash with Darren Reed, which resulted in the expulsion of IPF from the OpenBSD distribution.

As personal rivalries took precedence over a quality product, BSD's codebase became worse and worse. As we all know, incompatibilities between each BSD distribution make code sharing an arduous task. Research conducted at MIT found BSD's filesystem implementation to be "very poorly performing." Even BSD's acclaimed TCP/IP stack has lagged behind, according to this study.

Problems with BSD's codebase were compounded by fundamental flaws in the BSD design approach. As argued by Eric Raymond in his watershed essay, The Cathedral and the Bazaar, rapid, decentralized development models are inherently superior to slow, centralized ones in software development. BSD developers never heeded Mr. Raymond's lesson and insisted that centralized models lead to 'cleaner code.' Don't believe their hype - BSD's development model has significantly impaired its progress. Any achievements that BSD managed to make were nullified by the BSD license, which allows corporations and coders alike to reap profits without reciprocating the goodwill of open-source. Fortunately, Linux is not prone to this exploitation, as it is licensed under the GPL.

The failure of BSD culminated in the resignation of Jordan Hubbard and Michael Smith from the FreeBSD core team. They both believed that FreeBSD had long lost its earlier vitality. Like an empire in decline, BSD had become bureaucratic and stagnant. As Linux gains market share and as BSD sinks deeper into the mire of decay, their parting addresses will resound as fitting eulogies to BSD's demise.

Everyone knows aboutBSD's failure and imminent demise. As we pore over the history of BSD, we'll uncover a story of fatal mistakes, poor priorities, and personal rivalry, and we'll learn what mistakes to void so as to save Linux from a similarly grisly fate.

Let's not be overly morbid and give BSD credit for its early successes. In the 1970s, Ken Thompson and Bill Joy both made significant contributions to the computing world on the BSD platform. In the 80s, DARPA saw BSD as the premiere open platform, and, after initial successes with the 4.1BSD product, gave the BSD company a 2 year contract.

These early triumphs would soon be forgotten in a series of internal conflicts that would mar BSD's progress. In 1992, AT&T filed suit against Berkeley Software, claiming that proprietary code agreements had been haphazardly violated. In the same year, BSD filed countersuit, reciprocating bad intentions and fueling internal rivalry. While AT&T and Berkeley Software lawyers battled in court, lead developers of various BSD distributions quarreled on Usenet. In 1995, Theo de Raadt, one of the founders of the NetBSD project, formed his own rival distribution, OpenBSD, as the result of a quarrel that he documents on his website. Mr. de Raadt's stubborn arrogance was later seen in his clash with Darren Reed, which resulted in the expulsion of IPF from the OpenBSD distribution.

As personal rivalries took precedence over a quality product, BSD's codebase became worse and worse. As we all know, incompatibilities between each BSD distribution make code sharing an arduous task. Research conducted at MIT found BSD's filesystem implementation to be "very poorly performing." Even BSD's acclaimed TCP/IP stack has lagged behind, according to this study.

Problems with BSD's codebase were compounded by fundamental flaws in the BSD design approach. As argued by Eric Raymond in his watershed essay, The Cathedral and the Bazaar, rapid, decentralized development models are inherently superior to slow, centralized ones in software development. BSD developers never heeded Mr. Raymond's lesson and insisted that centralized models lead to 'cleaner code.' Don't believe their hype - BSD's development model has significantly impaired its progress. Any achievements that BSD managed to make were nullified by the BSD license, which allows corporations and coders alike to reap profits without reciprocating the goodwill of open-source. Fortunately, Linux is not prone to this exploitation, as it is licensed under the GPL.

The failure of BSD culminated in the resignation of Jordan Hubbard and Michael Smith from the FreeBSD core team. They both believed that FreeBSD had long lost its earlier vitality. Like an empire in decline, BSD had become bureaucratic and stagnant. As Linux gains market share and as BSD sinks deeper into the mire of decay, their parting addresses will resound as fitting eulogies to BSD's demise.

What We Can Learn From BSD
By Chinese Karma Whore, Version 1.0

Everyone knows about BSD's failure and imminent demise. As we pore over the history of BSD, we'll uncover a story of fatal mistakes, poor priorities, and personal rivalry, and we'll learn what mistakes to avoid so as to save Linux from a similarly grisly fate.

Let's not be overly morbid and give BSD credit for its early successes. In the 1970s, Ken Thompson and Bill Joy both made significant contributions to the computing world on the BSD platform. In the 80s, DARPA saw BSD as the premiere open platform, and, after initial successes with the 4.1BSD product, gave the BSD company a 2 year contract.

These early triumphs would soon be forgotten in a series of internal conflicts that would mar BSD's progress. In 1992, AT&T filed suit against Berkeley Software, claiming that proprietary code agreements had been haphazardly violated. In the same year, BSD filed countersuit, reciprocating bad intentions and fueling internal rivalry. While AT&T and Berkeley Software lawyers battled in court, lead developers of various BSD distributions quarreled on Usenet. In 1995, Theo de Raadt, one of the founders of the NetBSD project, formed his own rival distribution, OpenBSD, as the result of a quarrel that he documents on his website. Mr. de Raadt's stubborn arrogance was later seen in his clash with Darren Reed, which resulted in the expulsion of IPF from the OpenBSD distribution.

As personal rivalries took precedence over a quality product, BSD's codebase became worse and worse. As we all know, incompatibilities between each BSD distribution make code sharing an arduous task. Research conducted at MIT found BSD's filesystem implementation to be "very poorly performing." Even BSD's acclaimed TCP/IP stack has lagged behind, according to this study.

Problems with BSD's codebase were compounded by fundamental flaws in the BSD design approach. As argued by Eric Raymond in his watershed essay, The Cathedral and the Bazaar, rapid, decentralized development models are inherently superior to slow, centralized ones in software development. BSD developers never heeded Mr. Raymond's lesson and insisted that centralized models lead to 'cleaner code.' Don't believe their hype - BSD's development model has significantly impaired its progress. Any achievements that BSD managed to make were nullified by the BSD license, which allows corporations and coders alike to reap profits without reciprocating the goodwill of open-source. Fortunately, Linux is not prone to this exploitation, as it is licensed under the GPL.

The failure of BSD culminated in the resignation of Jordan Hubbard and Michael Smith from the FreeBSD core team. They both believed that FreeBSD had long lost its earlier vitality. Like an empire in decline, BSD had become bureacratic and stagnant. As Linux gains market share and as BSD sinks deeper into the mire of decay, their parting addresses will resound as fitting eulogies to BSD's demise.

What We Can Learn From BSD
By Chinese Karma Whore, Version 1.0

Everyone knows about BSD's failure and imminent demise. As we pore over the history of BSD, we'll uncover a story of fatal mistakes, poor priorities, and personal rivalry, and we'll learn what mistakes to avoid so as to save Linux from a similarly grisly fate.

Let's not be overly morbid and give BSD credit for its early successes. In the 1970s, Ken Thompson and Bill Joy both made significant contributions to the computing world on the BSD platform. In the 80s, DARPA saw BSD as the premiere open platform, and, after initial successes with the 4.1BSD product, gave the BSD company a 2 year contract.

These early triumphs would soon be forgotten in a series of internal conflicts that would mar BSD's progress. In 1992, AT&T filed suit against Berkeley Software, claiming that proprietary code agreements had been haphazardly violated. In the same year, BSD filed countersuit, reciprocating bad intentions and fueling internal rivalry. While AT&T and Berkeley Software lawyers battled in court, lead developers of various BSD distributions quarreled on Usenet. In 1995, Theo de Raadt, one of the founders of the NetBSD project, formed his own rival distribution, OpenBSD, as the result of a quarrel that he documents on his website. Mr. de Raadt's stubborn arrogance was later seen in his clash with Darren Reed, which resulted in the expulsion of IPF from the OpenBSD distribution.

As personal rivalries took precedence over a quality product, BSD's codebase became worse and worse. As we all know, incompatibilities between each BSD distribution make code sharing an arduous task. Research conducted at MIT found BSD's filesystem implementation to be "very poorly performing." Even BSD's acclaimed TCP/IP stack has lagged behind, according to this study.

Problems with BSD's codebase were compounded by fundamental flaws in the BSD design approach. As argued by Eric Raymond in his watershed essay, The Cathedral and the Bazaar, rapid, decentralized development models are inherently superior to slow, centralized ones in software development. BSD developers never heeded Mr. Raymond's lesson and insisted that centralized models lead to 'cleaner code.' Don't believe their hype - BSD's development model has significantly impaired its progress. Any achievements that BSD managed to make were nullified by the BSD license, which allows corporations and coders alike to reap profits without reciprocating the goodwill of open-source. Fortunately, Linux is not prone to this exploitation, as it is licensed under the GPL.

The failure of BSD culminated in the resignation of Jordan Hubbard and Michael Smith from the FreeBSD core team. They both believed that FreeBSD had long lost its earlier vitality. Like an empire in decline, BSD had become bureacratic and stagnant. As Linux gains market share and as BSD sinks deeper into the mire of decay, their parting addresses will resound as fitting eulogies to BSD's demise.

What We Can Learn From BSD

Everyone knows about BSD's failure and imminent demise. As we pore over the history of BSD, we'll uncover a story of fatal mistakes, poor priorities, and personal rivalry, and we'll learn what mistakes to avoid so as to save Linux from a similarly grisly fate.

Let's not be overly morbid and give BSD credit for its early successes. In the 1970s, Ken Thompson and Bill Joy both made significant contributions to the computing world on the BSD platform. In the 80s, DARPA saw BSD as the premiere open platform, and, after initial successes with the 4.1BSD product, gave the BSD company a 2 year contract.

These early triumphs would soon be forgotten in a series of internal conflicts that would mar BSD's progress. In 1992, AT&T filed suit against Berkeley Software, claiming that proprietary code agreements had been haphazardly violated. In the same year, BSD filed countersuit, reciprocating bad intentions and fueling internal rivalry. While AT&T and Berkeley Software lawyers battled in court, lead developers of various BSD distributions quarreled on Usenet. In 1995, Theo de Raadt, one of the founders of the NetBSD project, formed his own rival distribution, OpenBSD, as the result of a quarrel that he documents on his website. Mr. de Raadt's stubborn arrogance was later seen in his clash with Darren Reed, which resulted in the expulsion of IPF from the OpenBSD distribution.

As personal rivalries took precedence over a quality product, BSD's codebase became worse and worse. As we all know, incompatibilities between each BSD distribution make code sharing an arduous task. Research conducted at MIT found BSD's filesystem implementation to be "very poorly performing." Even BSD's acclaimed TCP/IP stack has lagged behind, according to this study.

Problems with BSD's codebase were compounded by fundamental flaws in the BSD design approach. As argued by Eric Raymond in his watershed essay, The Cathedral and the Bazaar, rapid, decentralized development models are inherently superior to slow, centralized ones in software development. BSD developers never heeded Mr. Raymond's lesson and insisted that centralized models lead to 'cleaner code.' Don't believe their hype - BSD's development model has significantly impaired its progress. Any achievements that BSD managed to make were nullified by the BSD license, which allows corporations and coders alike to reap profits without reciprocating the goodwill of open-source. Fortunately, Linux is not prone to this exploitation, as it is licensed under the GPL.

The failure of BSD culminated in the resignation of Jordan Hubbard and Michael Smith from the FreeBSD core team. They both believed that FreeBSD had long lost its earlier vitality. Like an empire in decline, BSD had become bureacratic and stagnant. As Linux gains market share and as BSD sinks deeper into the mire of decay, their parting addresses will resound as fitting eulogies to BSD's demise.

• WEP (Wired Equivalent Protocol)
• Open Systems Authentication
• Shared Key Authentication
• Access Control Lists (MAC Address Lists)
• Closed Network Access Control (LUCENTS Proprietary Access Control)

• WEP has known vulnerabilities allowing someone to decrypt information in real-time after capturing about a days worth of traffic.
• Open Systems Authenticationhas "shown that the authentication management frames are sent in the clear even when WEP is enabled."
• Shared Key Authenitication has shown that it is rudimentary to capture the Initialization Vector since it is sent in the clear as part of a WEP frame.
• Standard Access Control Lists are easily circumvented by an attacker sniffing the network for a valid MAC and thus reprogramming their network card to an appropriate value to gain access to the network.
• The proprietary Closed Network Access Control list that LUCENT (and others)touts as "a system that will not send the network identification (SSID) as a broadcast, thereby mandating that someone KNOW the SSID before they can associate to the network," is inherently flawed since:

1. The most effective strategy would be to put your wireless access points into aIPSEC enabled DMZ, and have your wireless users tunnel into your network using a VPN. If your corporation doesn't already have a VPN infrastructure in place, it's going to cost you some money to implement. Even if you do have a VPN in place, and all of your clients already have the VPN software, there's going to be an extra effort associated with setting up a VLAN for your DMZ. But this solution adds a layer of encryption and authentication that could make a wireless network suitable for sensitive data.
2. Consider using an additional level of authentication, such as RADIUS, before you permit an association with your access points. While it's not part of the 802.11b standard, a number of companies are optionally including some provision for RADIUS authentication. Orinoco access points, for example, can enforce RADIUS authentication of MAC addresses to an external RADIUS server. Intermec access points include a built-in RADIUS server for up to 128 MAC addresses.( EAP (Extensible Authentication Protocol) is used to allow wireless clients to authenticate to RADIUS servers using a single sign-on. )
3. At an absolute minimum, even with it's vulnerabilities, you should enable WEP. Whether you implement 64-bit or 128-bit doesn't really matter too much, as it's not the encryption scheme that's determining how long it takes to crack it, but the number of possible Initialization Vectors. WEP is only a low barrier to entry, but it will keep out many of the casual hackers because there are so many other wireless networks that are wide open and easier targets.

University of Maryland Study: http://www.cs.umd.edu/~waa/wireless.pdf

Fluhrer, Mantin and Shamir Study: http://www.eyetap.org/~rguerra/toronto2001/rc4_ksa proc.pdf

AT&T Labs and Rice University Study: http://www.cs.rice.edu/~astubble/wep/wep_attack.ht ml

What We Can Learn From BSD
By Chinese Karma Whore, Version 1.0

Everyone knows about BSD's failure and imminent demise. As we pore over the history of BSD, we'll uncover a story of fatal mistakes, poor priorities, and personal rivalry, and we'll learn what mistakes to avoid so as to save Linux from a similarly grisly fate.

Let's not be overly morbid and give BSD credit for its early successes. In the 1970s, Ken Thompson and Bill Joy both made significant contributions to the computing world on the BSD platform. In the 80s, DARPA saw BSD as the premiere open platform, and, after initial successes with the 4.1BSD product, gave the BSD company a 2 year contract.

These early triumphs would soon be forgotten in a series of internal conflicts that would mar BSD's progress. In 1992, AT&T filed suit against Berkeley Software, claiming that proprietary code agreements had been haphazardly violated. In the same year, BSD filed countersuit, reciprocating bad intentions and fueling internal rivalry. While AT&T and Berkeley Software lawyers battled in court, lead developers of various BSD distributions quarreled on Usenet. In 1995, Theo de Raadt, one of the founders of the NetBSD project, formed his own rival distribution, OpenBSD, as the result of a quarrel that he documents on his website. Mr. de Raadt's stubborn arrogance was later seen in his clash with Darren Reed, which resulted in the expulsion of IPF from the OpenBSD distribution.

As personal rivalries took precedence over a quality product, BSD's codebase became worse and worse. As we all know, incompatibilities between each BSD distribution make code sharing an arduous task. Research conducted at MIT found BSD's filesystem implementation to be "very poorly performing." Even BSD's acclaimed TCP/IP stack has lagged behind, according to this study.

Problems with BSD's codebase were compounded by fundamental flaws in the BSD design approach. As argued by Eric Raymond in his watershed essay, The Cathedral and the Bazaar, rapid, decentralized development models are inherently superior to slow, centralized ones in software development. BSD developers never heeded Mr. Raymond's lesson and insisted that centralized models lead to 'cleaner code.' Don't believe their hype - BSD's development model has significantly impaired its progress. Any achievements that BSD managed to make were nullified by the BSD license, which allows corporations and coders alike to reap profits without reciprocating the goodwill of open-source. Fortunately, Linux is not prone to this exploitation, as it is licensed under the GPL.

The failure of BSD culminated in the resignation of Jordan Hubbard and Michael Smith from the FreeBSD core team. They both believed that FreeBSD had long lost its earlier vitality. Like an empire in decline, BSD had become bureacratic and stagnant. As Linux gains market share and as BSD sinks deeper into the mire of decay, their parting addresses will resound as fitting eulogies to BSD's demise.

What We Can Learn From BSD

Everyone knows about BSD's failure and imminent demise. As we pore over the history of BSD, we'll uncover a story of fatal mistakes, poor priorities, and personal rivalry, and we'll learn what mistakes to avoid so as to save Linux from a similarly grisly fate.

Let's not be overly morbid and give BSD credit for its early successes. In the 1970s, Ken Thompson and Bill Joy both made significant contributions to the computing world on the BSD platform. In the 80s, DARPA saw BSD as the premiere open platform, and, after initial successes with the 4.1BSD product, gave the BSD company a 2 year contract.

BSD's early triumphs would soon be forgotten in a series of internal conflicts that would mar BSD's progress. In 1992, AT&T filed suit against Berkeley Software, claiming that proprietary code agreements had been haphazardly violated. In the same year, BSD filed countersuit, reciprocating bad intentions and fueling internal rivalry. While AT&T and Berkeley Software lawyers battled in court, lead developers of various BSD distributions quarreled on Usenet. In 1995, Theo de Raadt, one of the founders of the NetBSD project, formed his own rival distribution, OpenBSD, as the result of a quarrel that he documents on his website. Mr. de Raadt's stubborn arrogance was later seen in his clash with Darren Reed, which resulted in the expulsion of IPF from the OpenBSD distribution.

As personal rivalries took precedence over a quality product, BSD's codebase became worse and worse. As we all know, incompatibilities between each BSD distribution make code sharing an arduous task. Research conducted at MIT found BSD's filesystem implementation to be "very poorly performing." Even BSD's acclaimed TCP/IP stack has lagged behind, according to this study.

Problems with BSD's codebase were compounded by fundamental flaws in the BSD design approach. As argued by Eric Raymond in his watershed essay, The Cathedral and the Bazaar, rapid, decentralized development models are inherently superior to slow, centralized ones in software development. BSD developers never heeded Mr. Raymond's lesson and insisted that centralized models lead to 'cleaner code.' Don't believe their hype - BSD's development model has significantly impaired its progress. Any achievements that BSD managed to make were nullified by the BSD license, which allows corporations and coders alike to reap profits without reciprocating the goodwill of open-source. Fortunately, Linux is not prone to this exploitation, as it is licensed under the GPL.

The failure of BSD culminated in the resignation of Jordan Hubbard and Michael Smith from the FreeBSD core team. They both believed that FreeBSD had long lost its earlier vitality. Like an empire in decline, BSD had become bureacratic and stagnant. As Linux gains market share and as BSD sinks deeper into the mire of decay, their parting addresses will resound as fitting eulogies to BSD's demise.

Everyone knows about BSD's failure and imminent demise. He who ignores history is doomed to repeat it; as we pore over the history of BSD, we'll uncover a story of fatal mistakes, poor priorities, and personal rivalry, and we'll learn what mistakes to avoid so as to save Linux from a similarly grisly fate.

Let's not be overly morbid and give BSD credit for its early successes. In the 1970s, Ken Thompson and Bill Joy both made significant contributions to the computing world on the BSD platform. In the 80s, DARPA saw BSD as the premiere open platform, and, after initial successes with the 4.1BSD product, gave the BSD company a 2 year contract.

BSD's early triumphs would soon be forgotten in a series of

While AT&T and Berkeley Software lawyers battled in court, lead developers of various BSD distributions quarreled on Usenet. In 1995, Theo de Raadt, one of the founders of the NetBSD project, formed his own rival distribution, OpenBSD, as the result of a quarrel that he documents on his website. Mr. de Raadt's stubborn arrogance was later seen in his clash with Darren Reed, which resulted in the expulsion of IPF from the OpenBSD distribution.

As personal rivalries took precedence over a quality product, BSD's codebase became . Research conducted at MIT found BSD's filesystem implementation to be "very poorly performing." Even BSD's acclaimed TCP/IP stack has lagged behind, according to this study.

Problems with BSD's codebase were compounded by fundamental flaws in the BSD design approach.

The failure of BSD culminated in the resignation of Jordan Hubbard and Michael Smith from the FreeBSD core team. They both believed that FreeBSD had long lost its earlier vitality. Like an empire in decline, BSD had become too bureacratic and stagnant. As Linux gains market share and as BSD sinks deeper into the mire of decay, their parting addresses will resound as fitting eulogies to BSD's demise.

There is hope of more Knuth!

http://www.rice.edu/cb/sos/ -- Information pertaining to the effect of the CARP recomendations upon non-commerical radio stations.

http://www.kurthanson.com/ -- RAIN is a trade publication for the Internet Radio industry. This is an excellent site to keep tabs on how the campaign is going to stop these fees and reporting requirements.

http://broadcastpromotions.net/carp/ -- This site allows you to send faxes through their web site and directly to the person in Washington that you should be bugging.

The CARP proposal, if passed, will take effect on or about May 21, 2002.

It's a well known fact, however it's incorrect. There's no evidence that Gallileo used Pisa for dropping weights. It's more likely he used an inclined plane.

Quick: A Carbon Nanotube is a molecule of Carbon in the shape of a tube, a few nanometrea across and possibly infinitely long.

Helpful: Carbon Nanotubes are a varient of buckminsterfullerene. Molecules of which are made of 60 carbon atoms in a sephircal arrangement (like a british (soccar) football). Their exetremely tough, and have great potential for drug delivery and lubricant applications. Carbon Nanotubes split the fullerene molecule in half and extend it with a cylinder of carbon atoms. Another way to think of them is by imagining a rolled up sheet of grphite and capping the ends. Some pictures might make things clearer.

Nano is the next step from micro, current microchips are in the 0.1 micrometre range, this is the same as 100 nanometres. Carbon nanotubes are only a few (ie less than 10) nanometres across.

The article discusses single walled nanotubes, the other varient is multiwalled nanotubes, which are simply many nanotubes wrpped in layers - like a telescopic radio ariel. The potential of carbon nanotubes lies in making lots of them long and all in the same orientation, then we have a rope stronger than diamond (think space elevator strong). Also they might be used in nano scale electronics.

Hope that helps

Alex

According to the stats midway through the article, Bruno (presumably Rennisance philosopher Giordano Bruno) is searched for on Google more often than either Einstein or Freud. Now, I'm a bit fond of Il Nolano myself, but I rather thought he was rather obscure to people who haven't read Aegypt or Finnegan's Wake.

I think you meant this.

You could certainly do the same thing in Java, but it would not necessarilly be faster or better in any clear way. Most of the performance issues on Slashdot are probably from the database interaction. Some clever caching helps in those situations, but the particular language in use doesn't make much difference.

There is a great deal of dissent, even within the Java world, about the use of EJBs. Using them to model data gives relatively poor performance, while using nothing but stateless session beans makes them little more than RMI + JavaBeans with extra overhead. Recently there was an interesting report released from Rice University, which showed that in their benchmarks of a bookstore and an auction application, PHP (yes, a simple scripting language) outperformed Java servlets, and plain Java servlets outperformed EJBs. IBM has released benchmarks saying similar things and advises their consultants to stick with plain servlets when at all possible, and just use JavaBeans for modelling data.

All this to say, don't be so quick to put down programming languages that you haven't done any real projects with. Perl (or Python, or PHP, or whatever) might not be your style, but there's no reason to think it can't power a site like Slashdot just as well as Java can. You can write good or bad code in any language.

There is lots of P2P Research going on.

Check this out:
http://www.cs.rice.edu/Conferences/IPTPS02/

This happened this month at MIT.

OK, maybe translating train schedules and restaurant menus is good. But street signs, especially, are supposed to be unambiguous, their meaning readily apparent to anyone, whether literate in their native language or not.

And does this thing work on signs that some redneck has shot holes in with a 12-gauge?

When did Bruce Sterling write The Hacker Crackdown? Ten years ago? This isn't exactly news. Incidentally, read Sterling's book if you haven't already -- it covers the early days of hacking AT&T unix systems, phone phreaking, the history of the US Secret Service and more. The EFF has it in a dozen-odd formats, there's an ebook version for the PalmReader, and just for grins you can even get it of The WELL's Gopher server(!).

When you are through, you have no contacts, and zero assets ~

Yah -- that's the secret to the Harvard MBA. The schooling isn't what makes it special; it's the contacts. Heck, for $33k/year (which isn't bad considering Rice's Executive MBA is $65k/year!), it is almost a steal.

This is version 0.6 of a troll HOWTO, sort of a companion piece to jsm's excellent troll FAQ. As a draft, comments and criticism are always welcome, if not appreciated :)

Section 1 - Trolling techniques

There are techniques used by successful trolls to elicit the maximum amount of responses from unthinking /.ers. This section is dedicated to explaining how to use these in the course of your trolls. Remember though, a great troll can break any or all of these and still be successful...

• Timing

  Because you're posting as an AC, your troll will generally be ignored in favour of posters using their accounts, and so getting in early is essential. A good guideline is to get into the first 20 posts, so that people reading the article will see the troll before it is swamped out. One way of increasing the speed with which you get your troll into play is to prepare them beforehand, and then quickly customise them for the current article. This is easier than it sounds since /. typically repeats stories with small variations and runs lots of similar stories.

  Note that this is why Jon Katz stories are pretty worthless as trolling material - by the time you've found the article and prepared a troll there's already 50+ posts on it, most of them flaming Jon Katz anyway :)

• Exposure

  Once you've got your troll in, you need people to actually read it. You also want replies - /.ers are more likely to read your troll if it starts a large thread. You also want to remember that some people have set their comment thresholds to values higher than 0 - to get the attention of these you either want to get your post moderated up (see Style, below) or get a reply which gets moderated up to 4 or 5, in which case your troll becomes visible to all.

• Accounts

  An alternative to the time-honoured tradition of AC trolling is that of creating a "troll" account. This gives you the advantage of posting at 1 rather than 0, and slashbots are more likely to take you seriously, especially if you at least sound reasonable. If you do this, try to avoid posting stuff where it is obvious you're a troll under the account - post it anoymously instead - some slightly more canny readers actually check your user info before they reply. Not many though :)

  The ultimate goal of the troll account is to secure the +1 bonus, which is currently received once you hit 26 points of Karma. To get there, employ the techniques of karma whoring that we see every day on /. and watch the karma roll in. And of course once you get the +1 bonus, the world is your oyster in terms of /. Posts made at a default of 2 hit even those people with the threshold of 2, are more likely to get moderated up even further if they are at all coherent, and people tend to lose their critical thinking abilities in the face of the +1 bonus. Milk it for all it's worth.

• Layout

  To get people reading it a troll needs to be easily readable. Make sure you break it down into easily digestible paragraphs, use HTML tags where appropriate (but always make sure you close them properly) and use whitespace appropriately.

• Size

  Generally a troll shouldn't be too short, otherwise it'll get lost in the crowd. A workable minimum is a couple of medium paragraphs. Conversely, it shouldn't be too long, or no-one will bother to read it. Keep it to a happy medium.

• Spelling

  Whilst spelling is important if you want the troll to be taken "seriously", key spelling mistakes can draw out the spelling zealots, especially if you mis-spell the name of a venerated /. hero, like Linus Torveldes or Richard Strawlman (thanks dmg). Related to this is the use of the wrong word, explaining an acronym as being something it isn't or making a word into an acronym even when it isn't.

• Subject

  The subject line needs to draw attention to your post without making it obvious that it is a troll. A simple statement of the main point of your argument can work here.

  Style

  Once you realise that most moderators don't bother to read past the first paragraph or two, you can use this fact to craft trolls that can be moderated up as "Insightful" (note that I mean this in the /. sense rather than the real-world sense). Start off fairly reasonable, making statements that are /. friendly and not being too controversial. As the troll goes on, make it more and more controversial, building it up for the coup de grace in the final paragraph.

• Linking

  As we all know, a post with links is considered "informative" by the /. crowd. Moderators love it, and they rarely check the links, so be sure to include as many as possible. And make them wrong - a link to the Perl website should instead point to the Python website instead, and vice versa. The other alternative to incorrect links is "useful" links to places like www.linux.org and i.e. places /.ers could never have found on their own :)

• Feeding

  The ideal troll requires no feeding - it runs on its own, generating flamewars between clueless /.ers for your amusement. But often a troll requires some help and so you should consider feeding it. Feeding is best reserved for people making either completely clueless responses, people making responses with holes in, or those wonderful people who write a 2000-word point-by-point rebuttal of your troll.

• Know your audience

  Always keep in mind the kind of things advocated on /. so that you can play on and against them. This is why anti-Linux, creationist, gun-loving, pro-corporation trolls work well - the vast majority of /.ers hold the opposite viewpoints. And if a few people agree with you, so much the better - it merely validates your viewpoint in the eyes of readers.

• Arrogance

  Be arrogant. You, as a troll, know that you're right. No other explanation could exist. The wronger the "fact", the more assertively you should state it. Make it clear that you are better than everyone else - you know the truth and they are just too stupid to realise it. Use plenty of sarcasm, and use "quotes" to show it to people too dumb to realise.

• Offensiveness

  Being offensive in your initial troll can be counter-productive - it causes moderators to mark you down as flamebait in general. But if you're feeding, then you can get away with calling /.ers all kinds of things. Make broad generalisations about /. readers - call them "long-haired Linux zealots", "socialist open-source bigots" or whatever. Stereotyping is encouraged - people always want to think that they're an individual, and will point this out to you given half a chance.

• Indifference

  Great for articles with a political or social bent, this kind of troll expresses complete indifference to the topic at hand, wondering who on Earth cares about it. An alternative method is to say that the topic only concerns a certain group of people - criminals, idiots, hackers (always use this instead of crackers) or whatever group you want to offend.

• Sympathy

  Appear to take the same stance as the people you're trying to troll - claim you're as much a fan of Linux as the next man, but... This way you can make all kinds of claims in the sure knowledge that you actually know what you're talking about. A great phrase to use here is "In my experience". Remember to act like all the things you're pointing out are unfortunate but true.

• The common touch

  Always accuse /.ers of being elitist. This is an easy thing to do seeing as a lot of them are. Claim that is their grandmother couldn't use it, then they are just into it to feel better than Joe Sixpack rather than "doing it for the average user". This is always great for working into anti-Linux trolls - attack command-line tools and poorly designed desktops.

• The 31337 touch

  The opposite of the above. Claim that technology or whatever is only for the elite of society and that any attempt to open it up for everyone is wrong, an attack on intellectualism and possibly even dangerous. If people were meant to understand these things then they would, and it's their fault if they're too stupid to learn.

• Contradiction

  Never be afraid to contradict yourself, even in the space of a single sentence. The phrases "I am a top programmer who codes in VB" or "I am a supporter of open source who uses NT at work and 95 at home" will be sure to get a response from some weenie smugly pointing out the contradiction. Confuse the issue more by engaging in contradiction when you are feeding - this will confuse /.ers who will then make even more stupid replies, leaving them even more wide open for response.

  Clues

  If you're feeling brave, give the reader clues that this is an obvious troll. The classic example here is dmg's stock phrase "I am often accused of trolling (whatever that is)", but also feel free to use phrases like "I have not read the article, and I don't know much about XYZ but I feel I must comment". If anyone responds to a troll with these kinds of clues in it, feel free to bask in the glow of knee-jerk /. responses.

• Denial

  If you're unlucky someone will accuse you of being a troll (surely not!) and try and ruin it for you. If you don't want it all to end there, then be sure to counter it by accusing them of being small-minded and petty, saying that it's easier for them to say it's a troll than to accept that people have different opinions. Be sure to say this in the subject line, especially if their subject was the infamous "YHBT. YHL. HAND."

• Claiming credit

  Given that /. has its community of regular trolls (hi guys!), it's only polite to publish your troll on one of the so-called "hidden" forums for all to see and admire. This way, you get to bask in the praise of other trolls, they get to contribute to your's if they want to, and you get an easy way to find the troll later on when you want to check on its progress :)

  As for when to post it, that's a matter of opinion really. You can either post it straight away or leave it will after people start biting. Remember that the troll forum is also frequented by non-trolls, and sometimes you may get a self-declared "troll-buster" try and expose you. But remember, /.ers always post before thinking, and often it doesn't matter at all.

  There is no real current forum at the moment thanks to various spammers hitting the sids, but try trolltalk, the original troll sid started by 80md and osm way back in the day. Generally all postings are done there as an AC, with your name at the end of the post. Include a link to the troll somewhere in the text, which ideally will be directly to the post and its replies - click on the #XX link in the thread to get there.

• Ending the troll

  Sometimes you just get bored with a troll, or people start posting genuinely thoughtful stuff in reply (it does happen). When this happens it might be time to own up to the troll with a helpful "YHBT. YHL. HAND." post. Sometimes people will carry on a discussion of the issue, and if you're really lucky (and it was a great troll) they will completely fail to believe you and carry on arguing. If that happens, pat yourself on the back for writing a great troll :)

• The cheap $3 crack

  Finally, when all else fails and your troll gets moderated down to (-1, Troll) within ten seconds of you posting it, the only honourable thing to do is to accuse the moderators of smoking the cheap $3 crack (again) and give up :(

Section 2 - Types of troll

1. The Maniac

   Probably the most popular kind of troll, the Maniac holds an opinion on something, and won't budge from that opinion no matter what evidence to the contrary is presented. If challenged, the Maniac will simply get more and more agitated and abusive, deriding his opponents as "idiots", "wrong-thinking", "dangerous" and "subversive". Generally the Maniac takes a position that opposes the prevalent /. beliefs, but a similar effect can be achieved by taking a typical /. viewpoint and pushing it to ridiculous extremes.

   Maniacs can be crafted for practically every article /. posts, although some are more obvious targets than others. Civil liberty articles, especially on things like censorship, DMCA, UCITA that really get /.ers riled up, are usually extremely fruitful grounds for a well-crafted maniac. The other obvious type of article is anything which could possibly involve religion, especially evolution :)

   Here are some fruitful avenues to explore:

   • The right-wing

     Always popular, the right-wing maniac (RWM) is a God-fearing, gun-toting, flag-waving American, and proud of it. They don't care about the rest of the world, unless it's to "prove" that America is better than everything else, and they cannot stand liberal whining over civil rights. They hate the moral decay of America and want it to revert into a nation of heterosexual, Christian whites like it was meant to be. Woe betide anyone that dares to suggest otherwise.

   • Religion

     There are two ways to approach this kind of maniac. The harder to pull off is the militant atheist, but this is quite common amongst /. posters and you would have to be very offensive to get this to work. Of course with religion trolls, the argument can go on for ever once it's started... The more common approach is the Christian fundamentalist. They are ignorant, intolerant and bigoted in the extreme. For them the Bible is the inerrant word of God revealed to man - it contains no flaws and no contradictions. Thus they are strict Creationists - mentions of evolution or cosmology will set them off on vitriolic rants. Flaming denunciations of anyone daring to contradict the "Word of God" are the way to go, and any kind of proof can always be ignored by appealing to "secular humanist brainwashing". And let's not forget, the USA is the greatest nation on Earth because it has the righteous power of Jesus Christ behind it.

   • Ideology

     Pick a philosophy, any philosophy. This troll is a troll with a cause - they have found some kind of ideological truth, and are out to expose every other philosophy as a sham. Whether it be libertarianism, objectivism, communism or capitalism, this troll will point out the obvious "flaws" in any other philosophies, whilst spouting dogma about their own. And the best thing is - you don't even need to know that much about what you're spouting - making doctrinaire mistakes will get both sides of the argument flaming you, adding to the fun.

   • Software

     This is an old favourite and crops up in many forms, covering the gamut from OS maniacs (Linux zealots, MS-apologists or embittered BSD fanatics), language maniacs (Pascal vs. C, C vs. C++, C++ vs. Java, Perl vs. Python, VB vs. everything), application maniacs(GIMP vs. Photoshop, Netscape vs. IE, vi vs. emacs) and also includes people who complain about how technology should only be for the 31337 hackers.Guns

     Americans love their guns, and will always fight passionately for their Constitutionally guarenteed rights to bear arms and shoot people. Even the slightest hint of criticism of this will bring down the wrath of a thousand and one enraged gun-owners on you, so it's always a great point to work into a troll :)

2. The Expert

   The Expert is someone who is "savvy" in their particular field, and is perfectly willing to give their opinion on any topic even vauguely related to their field. The Expert is most likely to be from a field which /.ers as a rule despise - the classic example is dumb marketing guy, but try consultants, lawyers, politicians, lobbyists, executives, journalists (just think Jon Katz). With this kind of troll sweeping statements with little content are the norm, along wire dire portents of future catastrophe and dark hints of "insider knowledge".

   Some possible angles to exploit:

   • Industry knowledge

     The expert knows the computing industry from the inside - as a long-term pro, they can dispense knowledge knowing that they can "speak for the industry". Their smug self-satisfaction is bound to annoy, as is any suggestion that things aren't the way that /.ers would like it - saying "Linux requires the rock-solid guarantee of a trusted company like Microsoft" or "Apache cannot be trusted for mission-critical enterprise platforms" is guaranteed to get you denials explaining exactly why you're wrong, in excruciating detail.

   • Helpful hints

     With their tech-savvy (or law-savvy or whatever) experience, the expert is obviously the best person to point out what's wrong with things or to give out useful "factual" information. In fact this probably works best with lawyer trolls - for all that /.ers protest "IANAL", they certainly seem to think they could be, and any mistakes you make will send them rushing to prove themselves by correcting you.

3. Offtopic Trolls

   Not really a "troll" in the strict Jargon File sense of the word, but they certainly should be included here :) This category includes parodies, offtopic weirdness any all kinds of amusing stuff. Not really my area of expertise, this stuff is mainly done by gnarphlager and opensourceman. Thanks to gnarphlager for this section.

   Offtopic trolls, like any other, come in almost as many colours as an iMac, but generally not as cute. But then again, a good offtopic "troll" can affect more people than a repulsive little gumdrop on your desk, because you need to have someone SEE your desk before they can react. Simple? Moreso than even my overblown prose could indicate. Some basic examples:

   1. The serial troll

      Write a story. Keep expanding it. It doesn't matter what article you post it under, so long as it's high up. If you want people to recognize you, pick a couple themes or symbols, and carry them on throughout the story. Other alternatives include back linking or including the entire story, but adding more each time. Be funny if you want. Or if you don't feel like being funny, just be really weird. Someone will react.

   2. The random troll

      This has nothing to do with anything. Be it a stream of consciousness rant, or a description of the corner of your desk. Another favorite is a monologue, read as if spoken from any one given entity to another. The more outlandish, the better (a pair of socks talking to a mousepad, for example). If you really wanted to be artsy, work in an actual metaphor or legitimate meaning behind it, but it's not necessary.

   3. The vaguely related troll

      Start out with a comment about the article. Have a definite opinion of it. Then, after a little while, disintegrate into randomness. All roads eventually can eventually lead to cheese (yum), Natalie Portman, cannibalism, toasters, squirrels, futons, you name it. All it takes is a little bit of creativity. Oh, and feel free to use other trolls' motifs. Open source and all that ;-)

   General tips:

   • If it's funny for a fleeting moment, then it's worth posting.
   • Puns. Puns are only less vile than mimes, but it's hard to mime on /. So feel free/obligated to litter your offtopic and random bits with puns. Hurt the bastards. And if they're sick enough to laugh at them, then they'll eventually end up here ;-)
   • Obscure cultural references and injokes are always good. SOMEONE will get them eventually.
   • Several drafts of a serial or random post are common, but true elegance is being able to come up with something on the spot that still makes the top 40 posts (on a post-heavy article)

Section 3 - Useful trolling links

The following links contain background information useful for trolls needing quick quotes and "expert" opinions to include.

1. General purpose links
   • ddi.digital.net/~gandalf/trollfaq.html - How to deal with USENET trolls - learn your enemy :)
   • www.don-lindsay-archive.org/skeptic/arguments.html - A List Of Fallacious Arguments - Learn them and use them liberally
   • www.altairiv.demon.co.uk/troll/trollfaq.html - USENET troll HOWTO
   • www.baiting.org - Baiting.org
   • www.fieldingtravel.com/df/index.htm - Fielding's DangerFinder - A guide to what and where's dangerous
   
   
2. Religious links
   • www.godhatesamerica.com/ - God Hates America
   • www.chalcedon.edu/creed.html - The Creed of Christian Reconstruction
   • www.demonbuster.com - How to cast out your demons and do spiritual warfare
   • riceinfo.rice.edu/armadillo/Sciacademy/riggins/thi ngs.htm - Things Creationists hate
   • www.icr.org/ - Institute for Creation Research
   • www.xenu.net - Operation Clambake - The fight against Scientology on the net
   • www.hom.net/~angels/ - Citizens for the Ten Commandments
   • www.bju.edu/rcnbc.html - The difference between Catholics and Christians
   • www.geocities.com/prazske00/biblequotes.html - Bible quotes by category
   
   
3. Political/economy links
   • www.aynrand.org - The Ayn Rand Institute
   • www.reason.com - Libertarian site
   • www.freerepublic.com - Right-wing stuff
   • www.jbs.org - Excellent site for all kinds of right-wingery
   • www.dack.com/web/bullshit.html - Web economy bullshit generator
   
   
4. Crackpot science links
   • www.fixedearth.com - The Earth Is Not Moving
   • www.jir.com/index.htm - The Journal of Irreproducible Results
   
   

This is version 0.6 of a troll HOWTO, sort of a companion piece to jsm's excellent troll FAQ. As a draft, comments and criticism are always welcome, if not appreciated :)

Section 1 - Trolling techniques

There are techniques used by successful trolls to elicit the maximum amount of responses from unthinking /.ers. This section is dedicated to explaining how to use these in the course of your trolls. Remember though, a great troll can break any or all of these and still be successful...

• Timing

  Because you're posting as an AC, your troll will generally be ignored in favour of posters using their accounts, and so getting in early is essential. A good guideline is to get into the first 20 posts, so that people reading the article will see the troll before it is swamped out. One way of increasing the speed with which you get your troll into play is to prepare them beforehand, and then quickly customise them for the current article. This is easier than it sounds since /. typically repeats stories with small variations and runs lots of similar stories.

  Note that this is why Jon Katz stories are pretty worthless as trolling material - by the time you've found the article and prepared a troll there's already 50+ posts on it, most of them flaming Jon Katz anyway :)

• Exposure

  Once you've got your troll in, you need people to actually read it. You also want replies - /.ers are more likely to read your troll if it starts a large thread. You also want to remember that some people have set their comment thresholds to values higher than 0 - to get the attention of these you either want to get your post moderated up (see Style, below) or get a reply which gets moderated up to 4 or 5, in which case your troll becomes visible to all.

• Accounts

  An alternative to the time-honoured tradition of AC trolling is that of creating a "troll" account. This gives you the advantage of posting at 1 rather than 0, and slashbots are more likely to take you seriously, especially if you at least sound reasonable. If you do this, try to avoid posting stuff where it is obvious you're a troll under the account - post it anoymously instead - some slightly more canny readers actually check your user info before they reply. Not many though :)

  The ultimate goal of the troll account is to secure the +1 bonus, which is currently received once you hit 26 points of Karma. To get there, employ the techniques of karma whoring that we see every day on /. and watch the karma roll in. And of course once you get the +1 bonus, the world is your oyster in terms of /. Posts made at a default of 2 hit even those people with the threshold of 2, are more likely to get moderated up even further if they are at all coherent, and people tend to lose their critical thinking abilities in the face of the +1 bonus. Milk it for all it's worth.

• Layout

  To get people reading it a troll needs to be easily readable. Make sure you break it down into easily digestible paragraphs, use HTML tags where appropriate (but always make sure you close them properly) and use whitespace appropriately.

• Size

  Generally a troll shouldn't be too short, otherwise it'll get lost in the crowd. A workable minimum is a couple of medium paragraphs. Conversely, it shouldn't be too long, or no-one will bother to read it. Keep it to a happy medium.

• Spelling

  Whilst spelling is important if you want the troll to be taken "seriously", key spelling mistakes can draw out the spelling zealots, especially if you mis-spell the name of a venerated /. hero, like Linus Torveldes or Richard Strawlman (thanks dmg). Related to this is the use of the wrong word, explaining an acronym as being something it isn't or making a word into an acronym even when it isn't.

• Subject

  The subject line needs to draw attention to your post without making it obvious that it is a troll. A simple statement of the main point of your argument can work here.

  Style

  Once you realise that most moderators don't bother to read past the first paragraph or two, you can use this fact to craft trolls that can be moderated up as "Insightful" (note that I mean this in the /. sense rather than the real-world sense). Start off fairly reasonable, making statements that are /. friendly and not being too controversial. As the troll goes on, make it more and more controversial, building it up for the coup de grace in the final paragraph.

• Linking

  As we all know, a post with links is considered "informative" by the /. crowd. Moderators love it, and they rarely check the links, so be sure to include as many as possible. And make them wrong - a link to the Perl website should instead point to the Python website instead, and vice versa. The other alternative to incorrect links is "useful" links to places like www.linux.org and i.e. places /.ers could never have found on their own :)

• Feeding

  The ideal troll requires no feeding - it runs on its own, generating flamewars between clueless /.ers for your amusement. But often a troll requires some help and so you should consider feeding it. Feeding is best reserved for people making either completely clueless responses, people making responses with holes in, or those wonderful people who write a 2000-word point-by-point rebuttal of your troll.

• Know your audience

  Always keep in mind the kind of things advocated on /. so that you can play on and against them. This is why anti-Linux, creationist, gun-loving, pro-corporation trolls work well - the vast majority of /.ers hold the opposite viewpoints. And if a few people agree with you, so much the better - it merely validates your viewpoint in the eyes of readers.

• Arrogance

  Be arrogant. You, as a troll, know that you're right. No other explanation could exist. The wronger the "fact", the more assertively you should state it. Make it clear that you are better than everyone else - you know the truth and they are just too stupid to realise it. Use plenty of sarcasm, and use "quotes" to show it to people too dumb to realise.

• Offensiveness

  Being offensive in your initial troll can be counter-productive - it causes moderators to mark you down as flamebait in general. But if you're feeding, then you can get away with calling /.ers all kinds of things. Make broad generalisations about /. readers - call them "long-haired Linux zealots", "socialist open-source bigots" or whatever. Stereotyping is encouraged - people always want to think that they're an individual, and will point this out to you given half a chance.

• Indifference

  Great for articles with a political or social bent, this kind of troll expresses complete indifference to the topic at hand, wondering who on Earth cares about it. An alternative method is to say that the topic only concerns a certain group of people - criminals, idiots, hackers (always use this instead of crackers) or whatever group you want to offend.

• Sympathy

  Appear to take the same stance as the people you're trying to troll - claim you're as much a fan of Linux as the next man, but... This way you can make all kinds of claims in the sure knowledge that you actually know what you're talking about. A great phrase to use here is "In my experience". Remember to act like all the things you're pointing out are unfortunate but true.

• The common touch

  Always accuse /.ers of being elitist. This is an easy thing to do seeing as a lot of them are. Claim that is their grandmother couldn't use it, then they are just into it to feel better than Joe Sixpack rather than "doing it for the average user". This is always great for working into anti-Linux trolls - attack command-line tools and poorly designed desktops.

• The 31337 touch

  The opposite of the above. Claim that technology or whatever is only for the elite of society and that any attempt to open it up for everyone is wrong, an attack on intellectualism and possibly even dangerous. If people were meant to understand these things then they would, and it's their fault if they're too stupid to learn.

• Contradiction

  Never be afraid to contradict yourself, even in the space of a single sentence. The phrases "I am a top programmer who codes in VB" or "I am a supporter of open source who uses NT at work and 95 at home" will be sure to get a response from some weenie smugly pointing out the contradiction. Confuse the issue more by engaging in contradiction when you are feeding - this will confuse /.ers who will then make even more stupid replies, leaving them even more wide open for response.

  Clues

  If you're feeling brave, give the reader clues that this is an obvious troll. The classic example here is dmg's stock phrase "I am often accused of trolling (whatever that is)", but also feel free to use phrases like "I have not read the article, and I don't know much about XYZ but I feel I must comment". If anyone responds to a troll with these kinds of clues in it, feel free to bask in the glow of knee-jerk /. responses.

• Denial

  If you're unlucky someone will accuse you of being a troll (surely not!) and try and ruin it for you. If you don't want it all to end there, then be sure to counter it by accusing them of being small-minded and petty, saying that it's easier for them to say it's a troll than to accept that people have different opinions. Be sure to say this in the subject line, especially if their subject was the infamous "YHBT. YHL. HAND."

• Claiming credit

  Given that /. has its community of regular trolls (hi guys!), it's only polite to publish your troll on one of the so-called "hidden" forums for all to see and admire. This way, you get to bask in the praise of other trolls, they get to contribute to your's if they want to, and you get an easy way to find the troll later on when you want to check on its progress :)

  As for when to post it, that's a matter of opinion really. You can either post it straight away or leave it will after people start biting. Remember that the troll forum is also frequented by non-trolls, and sometimes you may get a self-declared "troll-buster" try and expose you. But remember, /.ers always post before thinking, and often it doesn't matter at all.

  There is no real current forum at the moment thanks to various spammers hitting the sids, but try trolltalk, the original troll sid started by 80md and osm way back in the day. Generally all postings are done there as an AC, with your name at the end of the post. Include a link to the troll somewhere in the text, which ideally will be directly to the post and its replies - click on the #XX link in the thread to get there.

• Ending the troll

  Sometimes you just get bored with a troll, or people start posting genuinely thoughtful stuff in reply (it does happen). When this happens it might be time to own up to the troll with a helpful "YHBT. YHL. HAND." post. Sometimes people will carry on a discussion of the issue, and if you're really lucky (and it was a great troll) they will completely fail to believe you and carry on arguing. If that happens, pat yourself on the back for writing a great troll :)

• The cheap $3 crack

  Finally, when all else fails and your troll gets moderated down to (-1, Troll) within ten seconds of you posting it, the only honourable thing to do is to accuse the moderators of smoking the cheap $3 crack (again) and give up :(

Section 2 - Types of troll

1. The Maniac

   Probably the most popular kind of troll, the Maniac holds an opinion on something, and won't budge from that opinion no matter what evidence to the contrary is presented. If challenged, the Maniac will simply get more and more agitated and abusive, deriding his opponents as "idiots", "wrong-thinking", "dangerous" and "subversive". Generally the Maniac takes a position that opposes the prevalent /. beliefs, but a similar effect can be achieved by taking a typical /. viewpoint and pushing it to ridiculous extremes.

   Maniacs can be crafted for practically every article /. posts, although some are more obvious targets than others. Civil liberty articles, especially on things like censorship, DMCA, UCITA that really get /.ers riled up, are usually extremely fruitful grounds for a well-crafted maniac. The other obvious type of article is anything which could possibly involve religion, especially evolution :)

   Here are some fruitful avenues to explore:

   • The right-wing

     Always popular, the right-wing maniac (RWM) is a God-fearing, gun-toting, flag-waving American, and proud of it. They don't care about the rest of the world, unless it's to "prove" that America is better than everything else, and they cannot stand liberal whining over civil rights. They hate the moral decay of America and want it to revert into a nation of heterosexual, Christian whites like it was meant to be. Woe betide anyone that dares to suggest otherwise.

   • Religion

     There are two ways to approach this kind of maniac. The harder to pull off is the militant atheist, but this is quite common amongst /. posters and you would have to be very offensive to get this to work. Of course with religion trolls, the argument can go on for ever once it's started... The more common approach is the Christian fundamentalist. They are ignorant, intolerant and bigoted in the extreme. For them the Bible is the inerrant word of God revealed to man - it contains no flaws and no contradictions. Thus they are strict Creationists - mentions of evolution or cosmology will set them off on vitriolic rants. Flaming denunciations of anyone daring to contradict the "Word of God" are the way to go, and any kind of proof can always be ignored by appealing to "secular humanist brainwashing". And let's not forget, the USA is the greatest nation on Earth because it has the righteous power of Jesus Christ behind it.

   • Ideology

     Pick a philosophy, any philosophy. This troll is a troll with a cause - they have found some kind of ideological truth, and are out to expose every other philosophy as a sham. Whether it be libertarianism, objectivism, communism or capitalism, this troll will point out the obvious "flaws" in any other philosophies, whilst spouting dogma about their own. And the best thing is - you don't even need to know that much about what you're spouting - making doctrinaire mistakes will get both sides of the argument flaming you, adding to the fun.

   • Software

     This is an old favourite and crops up in many forms, covering the gamut from OS maniacs (Linux zealots, MS-apologists or embittered BSD fanatics), language maniacs (Pascal vs. C, C vs. C++, C++ vs. Java, Perl vs. Python, VB vs. everything), application maniacs(GIMP vs. Photoshop, Netscape vs. IE, vi vs. emacs) and also includes people who complain about how technology should only be for the 31337 hackers.Guns

     Americans love their guns, and will always fight passionately for their Constitutionally guarenteed rights to bear arms and shoot people. Even the slightest hint of criticism of this will bring down the wrath of a thousand and one enraged gun-owners on you, so it's always a great point to work into a troll :)

2. The Expert

   The Expert is someone who is "savvy" in their particular field, and is perfectly willing to give their opinion on any topic even vauguely related to their field. The Expert is most likely to be from a field which /.ers as a rule despise - the classic example is dumb marketing guy, but try consultants, lawyers, politicians, lobbyists, executives, journalists (just think Jon Katz). With this kind of troll sweeping statements with little content are the norm, along wire dire portents of future catastrophe and dark hints of "insider knowledge".

   Some possible angles to exploit:

   • Industry knowledge

     The expert knows the computing industry from the inside - as a long-term pro, they can dispense knowledge knowing that they can "speak for the industry". Their smug self-satisfaction is bound to annoy, as is any suggestion that things aren't the way that /.ers would like it - saying "Linux requires the rock-solid guarantee of a trusted company like Microsoft" or "Apache cannot be trusted for mission-critical enterprise platforms" is guaranteed to get you denials explaining exactly why you're wrong, in excruciating detail.

   • Helpful hints

     With their tech-savvy (or law-savvy or whatever) experience, the expert is obviously the best person to point out what's wrong with things or to give out useful "factual" information. In fact this probably works best with lawyer trolls - for all that /.ers protest "IANAL", they certainly seem to think they could be, and any mistakes you make will send them rushing to prove themselves by correcting you.

   Offtopic Trolls

   Not really a "troll" in the strict Jargon File sense of the word, but they certainly should be included here :) This category includes parodies, offtopic weirdness any all kinds of amusing stuff. Not really my area of expertise, this stuff is mainly done by gnarphlager and opensourceman. Thanks to gnarphlager for this section.

   Offtopic trolls, like any other, come in almost as many colours as an iMac, but generally not as cute. But then again, a good offtopic "troll" can affect more people than a repulsive little gumdrop on your desk, because you need to have someone SEE your desk before they can react. Simple? Moreso than even my overblown prose could indicate. Some basic examples:

   1. The serial troll

      Write a story. Keep expanding it. It doesn't matter what article you post it under, so long as it's high up. If you want people to recognize you, pick a couple themes or symbols, and carry them on throughout the story. Other alternatives include back linking or including the entire story, but adding more each time. Be funny if you want. Or if you don't feel like being funny, just be really weird. Someone will react.

   2. The random troll

      This has nothing to do with anything. Be it a stream of consciousness rant, or a description of the corner of your desk. Another favorite is a monologue, read as if spoken from any one given entity to another. The more outlandish, the better (a pair of socks talking to a mousepad, for example). If you really wanted to be artsy, work in an actual metaphor or legitimate meaning behind it, but it's not necessary.

   3. The vaguely related troll

      Start out with a comment about the article. Have a definite opinion of it. Then, after a little while, disintegrate into randomness. All roads eventually can eventually lead to cheese (yum), Natalie Portman, cannibalism, toasters, squirrels, futons, you name it. All it takes is a little bit of creativity. Oh, and feel free to use other trolls' motifs. Open source and all that ;-)

   General tips:

   • If it's funny for a fleeting moment, then it's worth posting.
   • Puns. Puns are only less vile than mimes, but it's hard to mime on /. So feel free/obligated to litter your offtopic and random bits with puns. Hurt the bastards. And if they're sick enough to laugh at them, then they'll eventually end up here ;-)
   • Obscure cultural references and injokes are always good. SOMEONE will get them eventually.
   • Several drafts of a serial or random post are common, but true elegance is being able to come up with something on the spot that still makes the top 40 posts (on a post-heavy article)

Section 3 - Useful trolling links

The following links contain background information useful for trolls needing quick quotes and "expert" opinions to include.

1. General purpose links
   • ddi.digital.net/~gandalf/trollfaq.html - How to deal with USENET trolls - learn your enemy :)
   • www.don-lindsay-archive.org/skeptic/arguments.html - A List Of Fallacious Arguments - Learn them and use them liberally
   • www.altairiv.demon.co.uk/troll/trollfaq.html - USENET troll HOWTO
   • www.baiting.org - Baiting.org
   • www.fieldingtravel.com/df/index.htm - Fielding's DangerFinder - A guide to what and where's dangerous
   
   
2. Religious links
   • www.godhatesamerica.com/ - God Hates America
   • www.chalcedon.edu/creed.html - The Creed of Christian Reconstruction
   • www.demonbuster.com - How to cast out your demons and do spiritual warfare
   • riceinfo.rice.edu/armadillo/Sciacademy/riggins/thi ngs.htm - Things Creationists hate
   • www.icr.org/ - Institute for Creation Research
   • www.xenu.net - Operation Clambake - The fight against Scientology on the net
   • www.hom.net/~angels/ - Citizens for the Ten Commandments
   • www.bju.edu/rcnbc.html - The difference between Catholics and Christians
   • www.geocities.com/prazske00/biblequotes.html - Bible quotes by category
   
   
3. Political/economy links
   • www.aynrand.org - The Ayn Rand Institute
   • www.reason.com - Libertarian site
   • www.freerepublic.com - Right-wing stuff
   • www.jbs.org - Excellent site for all kinds of right-wingery
   • www.dack.com/web/bullshit.html - Web economy bullshit generator
   
   
4. Crackpot science links
   • www.fixedearth.com - The Earth Is Not Moving
   • www.jir.com/index.htm - The Journal of Irreproducible Results
   
   

He should have checked out the MSDN docs. He should also have read some security studies or even done his own. Perhaps then he would have realized that the security of the CLR has nothing to do with an arbitrary bit set to mark a block of code as "safe", but rather to do with a type-safety verifier that is completely independent of the compiler and language used to generate the code in question.

C# is not tied to the CLR like Java is tied to the JVM. The CLR (Common Language Runtime) is designed to run IL code, and there are compilers for many different languages besides just C# that can generate IL. That said, it should be clear that the security of a C# program is not derived from the C# compiler. It comes from the CLR, so the security policy is enforced at the IL level, not prior to compilation. (It would be laughable if the security of the CLR was enforced only by the C# compiler rejecting "unsafe" code. I'd just write my own C# compiler that allowed it, or I'd whip out my IL assembler.)

The "unsafe" marking of code occurs only at the source code level. Whether or not code is considered type-safe by the CLR is not determined by an arbitrary flag set by the developer; it's a function of the IL code itself. It needs to be that way, otherwise programs compiled with my evil compiler for my own non-type-safe language would slip through the cracks. Note that even if my IL code is actually type-safe, if the CLR's type-safety verifier can't prove it, it won't be considered type-safe.

That being said, "unsafe" is just a compiler feature. Perhaps Bill Joy would have had nothing to say if Microsoft had decided to use a keyword other than "unsafe", like maybe "dont_generate_an_error_at_compile_time_if_the_cod e_inside_this_block_fails_the_type_safety_check_ev en_though_it_is_going_to_fail_when_the_CLR_tries_t o_run_it_in_a_context_that_requires_type_safety". (Actually you can achieve this if you don't mind adding a #define to your C# source and then running it through a C preprocessor first.)

But why take my word for it? Check out an interesting study into C# and the CLR's security done by some students at Rice University at http://www.owlnet.rice.edu/~jsinger/comp527/propos al.html. They have a lot of detail there about tests they ran, as well as a good paper summing up their results.

D

Section 1 - Trolling techniques

There are techniques used by successful trolls to elicit the maximum amount of responses from unthinking /.ers. This section is dedicated to explaining how to use these in the course of your trolls. Remember though, a great troll can break any or all of these and still be successful...

• Timing

  Because you're posting as an AC, your troll will generally be ignored in favour of posters using their accounts, and so getting in early is essential. A good guideline is to get into the first 20 posts, so that people reading the article will see the troll before it is swamped out. One way of increasing the speed with which you get your troll into play is to prepare them beforehand, and then quickly customise them for the current article. This is easier than it sounds since /. typically repeats stories with small variations and runs lots of similar stories.

  Note that this is why Jon Katz stories are pretty worthless as trolling material - by the time you've found the article and prepared a troll there's already 50+ posts on it, most of them flaming Jon Katz anyway :)

• Exposure

  Once you've got your troll in, you need people to actually read it. You also want replies - /.ers are more likely to read your troll if it starts a large thread. You also want to remember that some people have set their comment thresholds to values higher than 0 - to get the attention of these you either want to get your post moderated up (see Style, below) or get a reply which gets moderated up to 4 or 5, in which case your troll becomes visible to all.

• Accounts

  An alternative to the time-honoured tradition of AC trolling is that of creating a "troll" account. This gives you the advantage of posting at 1 rather than 0, and slashbots are more likely to take you seriously, especially if you at least sound reasonable. If you do this, try to avoid posting stuff where it is obvious you're a troll under the account - post it anoymously instead - some slightly more canny readers actually check your user info before they reply. Not many though :)

  The ultimate goal of the troll account is to secure the +1 bonus, which is currently received once you hit 26 points of Karma. To get there, employ the techniques of karma whoring that we see every day on /. and watch the karma roll in. And of course once you get the +1 bonus, the world is your oyster in terms of /. Posts made at a default of 2 hit even those people with the threshold of 2, are more likely to get moderated up even further if they are at all coherent, and people tend to lose their critical thinking abilities in the face of the +1 bonus. Milk it for all it's worth.

• Layout

  To get people reading it a troll needs to be easily readable. Make sure you break it down into easily digestible paragraphs, use HTML tags where appropriate (but always make sure you close them properly) and use whitespace appropriately.

• Size

  Generally a troll shouldn't be too short, otherwise it'll get lost in the crowd. A workable minimum is a couple of medium paragraphs. Conversely, it shouldn't be too long, or no-one will bother to read it. Keep it to a happy medium.

• Spelling

  Whilst spelling is important if you want the troll to be taken "seriously", key spelling mistakes can draw out the spelling zealots, especially if you mis-spell the name of a venerated /. hero, like Linus Torveldes or Richard Strawlman (thanks dmg). Related to this is the use of the wrong word, explaining an acronym as being something it isn't or making a word into an acronym even when it isn't.

• Subject

  The subject line needs to draw attention to your post without making it obvious that it is a troll. A simple statement of the main point of your argument can work here.

• Style

  Once you realise that most moderators don't bother to read past the first paragraph or two, you can use this fact to craft trolls that can be moderated up as "Insightful" (note that I mean this in the /. sense rather than the real-world sense). Start off fairly reasonable, making statements that are /. friendly and not being too controversial. As the troll goes on, make it more and more controversial, building it up for the coup de grace in the final paragraph.

• Linking

  As we all know, a post with links is considered "informative" by the /. crowd. Moderators love it, and they rarely check the links, so be sure to include as many as possible. And make them wrong - a link to the Perl website should instead point to the Python website instead, and vice versa. The other alternative to incorrect links is "useful" links to places like www.linux.org and www.microsoft.com i.e. places /.ers could never have found on their own :)

• Feeding

  The ideal troll requires no feeding - it runs on its own, generating flamewars between clueless /.ers for your amusement. But often a troll requires some help and so you should consider feeding it. Feeding is best reserved for people making either completely clueless responses, people making responses with holes in, or those wonderful people who write a 2000-word point-by-point rebuttal of your troll.

• Know your audience

  Always keep in mind the kind of things advocated on /. so that you can play on and against them. This is why anti-Linux, creationist, gun-loving, pro-corporation trolls work well - the vast majority of /.ers hold the opposite viewpoints. And if a few people agree with you, so much the better - it merely validates your viewpoint in the eyes of readers.

• Arrogance

  Be arrogant. You, as a troll, know that you're right. No other explanation could exist. The wronger the "fact", the more assertively you should state it. Make it clear that you are better than everyone else - you know the truth and they are just too stupid to realise it. Use plenty of sarcasm, and use "quotes" to show it to people too dumb to realise.

• Offensiveness

  Being offensive in your initial troll can be counter-productive - it causes moderators to mark you down as flamebait in general. But if you're feeding, then you can get away with calling /.ers all kinds of things. Make broad generalisations about /. readers - call them "long-haired Linux zealots", "socialist open-source bigots" or whatever. Stereotyping is encouraged - people always want to think that they're an individual, and will point this out to you given half a chance.

• Indifference

  Great for articles with a political or social bent, this kind of troll expresses complete indifference to the topic at hand, wondering who on Earth cares about it. An alternative method is to say that the topic only concerns a certain group of people - criminals, idiots, hackers (always use this instead of crackers) or whatever group you want to offend.

• Sympathy

  Appear to take the same stance as the people you're trying to troll - claim you're as much a fan of Linux as the next man, but... This way you can make all kinds of claims in the sure knowledge that you actually know what you're talking about. A great phrase to use here is "In my experience". Remember to act like all the things you're pointing out are unfortunate but true.

• The common touch

  Always accuse /.ers of being elitist. This is an easy thing to do seeing as a lot of them are. Claim that is their grandmother couldn't use it, then they are just into it to feel better than Joe Sixpack rather than "doing it for the average user". This is always great for working into anti-Linux trolls - attack command-line tools and poorly designed desktops.

• The 31337 touch

  The opposite of the above. Claim that technology or whatever is only for the elite of society and that any attempt to open it up for everyone is wrong, an attack on intellectualism and possibly even dangerous. If people were meant to understand these things then they would, and it's their fault if they're too stupid to learn.

• Contradiction

  Never be afraid to contradict yourself, even in the space of a single sentence. The phrases "I am a top programmer who codes in VB" or "I am a supporter of open source who uses NT at work and 95 at home" will be sure to get a response from some weenie smugly pointing out the contradiction. Confuse the issue more by engaging in contradiction when you are feeding - this will confuse /.ers who will then make even more stupid replies, leaving them even more wide open for response.

  Clues

  If you're feeling brave, give the reader clues that this is an obvious troll. The classic example here is dmg's stock phrase "I am often accused of trolling (whatever that is)", but also feel free to use phrases like "I have not read the article, and I don't know much about XYZ but I feel I must comment". If anyone responds to a troll with these kinds of clues in it, feel free to bask in the glow of knee-jerk /. responses.

• Denial

  If you're unlucky someone will accuse you of being a troll (surely not!) and try and ruin it for you. If you don't want it all to end there, then be sure to counter it by accusing them of being small-minded and petty, saying that it's easier for them to say it's a troll than to accept that people have different opinions. Be sure to say this in the subject line, especially if their subject was the infamous "YHBT. YHL. HAND."

• Claiming credit

  Given that /. has its community of regular trolls (hi guys!), it's only polite to publish your troll on one of the so-called "hidden" forums for all to see and admire. This way, you get to bask in the praise of other trolls, they get to contribute to your's if they want to, and you get an easy way to find the troll later on when you want to check on its progress :)

  As for when to post it, that's a matter of opinion really. You can either post it straight away or leave it will after people start biting. Remember that the troll forum is also frequented by non-trolls, and sometimes you may get a self-declared "troll-buster" try and expose you. But remember, /.ers always post before thinking, and often it doesn't matter at all.

  There is no real current forum at the moment thanks to various spammers hitting the sids, but try trolltalk, the original troll sid started by 80md and osm way back in the day. Generally all postings are done there as an AC, with your name at the end of the post. Include a link to the troll somewhere in the text, which ideally will be directly to the post and its replies - click on the #XX link in the thread to get there.

• Ending the troll

  Sometimes you just get bored with a troll, or people start posting genuinely thoughtful stuff in reply (it does happen). When this happens it might be time to own up to the troll with a helpful "YHBT. YHL. HAND." post. Sometimes people will carry on a discussion of the issue, and if you're really lucky (and it was a great troll) they will completely fail to believe you and carry on arguing. If that happens, pat yourself on the back for writing a great troll :)

• The cheap $3 crack

  Finally, when all else fails and your troll gets moderated down to (-1, Troll) within ten seconds of you posting it, the only honourable thing to do is to accuse the moderators of smoking the cheap $3 crack (again) and give up :(

Section 2 - Types of troll

1. The Maniac

   Probably the most popular kind of troll, the Maniac holds an opinion on something, and won't budge from that opinion no matter what evidence to the contrary is presented. If challenged, the Maniac will simply get more and more agitated and abusive, deriding his opponents as "idiots", "wrong-thinking", "dangerous" and "subversive". Generally the Maniac takes a position that opposes the prevalent /. beliefs, but a similar effect can be achieved by taking a typical /. viewpoint and pushing it to ridiculous extremes.

   Maniacs can be crafted for practically every article /. posts, although some are more obvious targets than others. Civil liberty articles, especially on things like censorship, DMCA, UCITA that really get /.ers riled up, are usually extremely fruitful grounds for a well-crafted maniac. The other obvious type of article is anything which could possibly involve religion, especially evolution :)

   Here are some fruitful avenues to explore:

   • The right-wing

     Always popular, the right-wing maniac (RWM) is a God-fearing, gun-toting, flag-waving American, and proud of it. They don't care about the rest of the world, unless it's to "prove" that America is better than everything else, and they cannot stand liberal whining over civil rights. They hate the moral decay of America and want it to revert into a nation of heterosexual, Christian whites like it was meant to be. Woe betide anyone that dares to suggest otherwise.

   • Religion

     There are two ways to approach this kind of maniac. The harder to pull off is the militant atheist, but this is quite common amongst /. posters and you would have to be very offensive to get this to work. Of course with religion trolls, the argument can go on for ever once it's started... The more common approach is the Christian fundamentalist. They are ignorant, intolerant and bigoted in the extreme. For them the Bible is the inerrant word of God revealed to man - it contains no flaws and no contradictions. Thus they are strict Creationists - mentions of evolution or cosmology will set them off on vitriolic rants. Flaming denunciations of anyone daring to contradict the "Word of God" are the way to go, and any kind of proof can always be ignored by appealing to "secular humanist brainwashing". And let's not forget, the USA is the greatest nation on Earth because it has the righteous power of Jesus Christ behind it.

   • Ideology

     Pick a philosophy, any philosophy. This troll is a troll with a cause - they have found some kind of ideological truth, and are out to expose every other philosophy as a sham. Whether it be libertarianism, objectivism, communism or capitalism, this troll will point out the obvious "flaws" in any other philosophies, whilst spouting dogma about their own. And the best thing is - you don't even need to know that much about what you're spouting - making doctrinaire mistakes will get both sides of the argument flaming you, adding to the fun.

   • Software

     This is an old favourite and crops up in many forms, covering the gamut from OS maniacs (Linux zealots, MS-apologists or embittered BSD fanatics), language maniacs (Pascal vs. C, C vs. C++, C++ vs. Java, Perl vs. Python, VB vs. everything), application maniacs(GIMP vs. Photoshop, Netscape vs. IE, vi vs. emacs) and also includes people who complain about how technology should only be for the 31337 hackers.

   • Guns

     Americans love their guns, and will always fight passionately for their Constitutionally guarenteed rights to bear arms and shoot people. Even the slightest hint of criticism of this will bring down the wrath of a thousand and one enraged gun-owners on you, so it's always a great point to work into a troll :)

2. The Expert

   The Expert is someone who is "savvy" in their particular field, and is perfectly willing to give their opinion on any topic even vauguely related to their field. The Expert is most likely to be from a field which /.ers as a rule despise - the classic example is dumb marketing guy, but try consultants, lawyers, politicians, lobbyists, executives, journalists (just think Jon Katz). With this kind of troll sweeping statements with little content are the norm, along wire dire portents of future catastrophe and dark hints of "insider knowledge".

   Some possible angles to exploit:

   • Industry knowledge

     The expert knows the computing industry from the inside - as a long-term pro, they can dispense knowledge knowing that they can "speak for the industry". Their smug self-satisfaction is bound to annoy, as is any suggestion that things aren't the way that /.ers would like it - saying "Linux requires the rock-solid guarantee of a trusted company like Microsoft" or "Apache cannot be trusted for mission-critical enterprise platforms" is guaranteed to get you denials explaining exactly why you're wrong, in excruciating detail.

   • Helpful hints

     With their tech-savvy (or law-savvy or whatever) experience, the expert is obviously the best person to point out what's wrong with things or to give out useful "factual" information. In fact this probably works best with lawyer trolls - for all that /.ers protest "IANAL", they certainly seem to think they could be, and any mistakes you make will send them rushing to prove themselves by correcting you.

3. Offtopic Trolls

   Not really a "troll" in the strict Jargon File sense of the word, but they certainly should be included here :) This category includes parodies, offtopic weirdness any all kinds of amusing stuff. Not really my area of expertise, this stuff is mainly done by gnarphlager and opensourceman. Thanks to gnarphlager for this section.

   Offtopic trolls, like any other, come in almost as many colours as an iMac, but generally not as cute. But then again, a good offtopic "troll" can affect more people than a repulsive little gumdrop on your desk, because you need to have someone SEE your desk before they can react. Simple? Moreso than even my overblown prose could indicate. Some basic examples:

   1. The serial troll

      Write a story. Keep expanding it. It doesn't matter what article you post it under, so long as it's high up. If you want people to recognize you, pick a couple themes or symbols, and carry them on throughout the story. Other alternatives include back linking or including the entire story, but adding more each time. Be funny if you want. Or if you don't feel like being funny, just be really weird. Someone will react.

   2. The random troll

      This has nothing to do with anything. Be it a stream of consciousness rant, or a description of the corner of your desk. Another favorite is a monologue, read as if spoken from any one given entity to another. The more outlandish, the better (a pair of socks talking to a mousepad, for example). If you really wanted to be artsy, work in an actual metaphor or legitimate meaning behind it, but it's not necessary.

   3. The vaguely related troll

      Start out with a comment about the article. Have a definite opinion of it. Then, after a little while, disintegrate into randomness. All roads eventually can eventually lead to cheese (yum), Natalie Portman, cannibalism, toasters, squirrels, futons, you name it. All it takes is a little bit of creativity. Oh, and feel free to use other trolls' motifs. Open source and all that ;-)

   General tips:

   • If it's funny for a fleeting moment, then it's worth posting.
   • Puns. Puns are only less vile than mimes, but it's hard to mime on /. So feel free/obligated to litter your offtopic and random bits with puns. Hurt the bastards. And if they're sick enough to laugh at them, then they'll eventually end up here ;-)
   • Obscure cultural references and injokes are always good. SOMEONE will get them eventually.
   • Several drafts of a serial or random post are common, but true elegance is being able to come up with something on the spot that still makes the top 40 posts (on a post-heavy article)

Section 3 - Useful trolling links

The following links contain background information useful for trolls needing quick quotes and "expert" opinions to include.

1. General purpose links
   • ddi.digital.net/~gandalf/trollfaq.html - How to deal with USENET trolls - learn your enemy :)
   • www.don-lindsay-archive.org/skeptic/arguments.html - A List Of Fallacious Arguments - Learn them and use them liberally
   • www.altairiv.demon.co.uk/troll/trollfaq.html - USENET troll HOWTO
   • www.baiting.org - Baiting.org
   • www.fieldingtravel.com/df/index.htm - Fielding's DangerFinder - A guide to what and where's dangerous
   
   
2. Religious links
   • www.godhatesamerica.com/ - God Hates America
   • www.chalcedon.edu/creed.html - The Creed of Christian Reconstruction
   • www.demonbuster.com - How to cast out your demons and do spiritual warfare
   • riceinfo.rice.edu/armadillo/Sciacademy/riggins/thi ngs.htm - Things Creationists hate
   • www.icr.org/ - Institute for Creation Research
   • www.xenu.net - Operation Clambake - The fight against Scientology on the net
   • www.hom.net/~angels/ - Citizens for the Ten Commandments
   • www.bju.edu/rcnbc.html - The difference between Catholics and Christians
   • www.geocities.com/prazske00/biblequotes.html - Bible quotes by category
   
   
3. Political/economy links
   • www.aynrand.org - The Ayn Rand Institute
   • www.reason.com - Libertarian site
   • www.freerepublic.com - Right-wing stuff
   • www.jbs.org - Excellent site for all kinds of right-wingery
   • www.dack.com/web/bullshit.html - Web economy bullshit generator
   
   
4. Crackpot science links
   • www.fixedearth.com - The Earth Is Not Moving
   • www.jir.com/index.htm - The Journal of Irreproducible Results
   
   

Along your point, there's actually a technique that uses the self similarity of images to help you compress themselves. For example, you might have seen the "Sierpinsky Triangle." You can generate this image with a few very simple recursive move/resize/draw operations.

Fractal compression uses this technique on abstract images. It aims to find a set of operations (sometimes very large) to generate any given input picture. It's very cool, and you can get more information (including example pictures) at this page.

The "state of the art" of fractal compression beats JPEG compression at some compression ratios, but looses at others. It's also interesting that a fractally-compressed image has no implicit size (ie: 640x460), so it enlarges MUCH better than simple image enlargement.

As an academic, he is just barely legitimate. If you have a net connection through a research university, you can look at his list of (mostly bogus) publications at mathscinet

Almost surely, this is a scheme to separate naive investors from their money.

One more in the didn't-get-anywhere-here's-my-entry-anyway camp...

"Spam"

See your inbox fill with spam
Endless spam
Counterfeited headers, and the path a hollow sham
See it flowing, flowing, flowing
From the corners of the net
And the frantic to-and-froing
Of abuse reports, though knowing
That they seldom pose a threat
Hear the ping! ping! ping!
Of your notifier sing
That another hundred emails have just broken through the dam
Full of spam, spam, spam, spam,
Spam, spam, spam
Full of maddening, infuriating spam

See the garbled string of spam
Foreign spam
In from every nation from the Congo to Siam
Promise unfamiliar joys
In a stream of random noise
That is spilt in wild array
Across your screen
At least one or two a day
And you haven't any idea what they say
Or they mean
Ah, the world is small indeed
What a joy to open up your inbox and to read
Fw:]s®QDVDKOeAI
Fw:¥ôÈDVDKOeAI [note the clever triple rhyme - ed.]
Dripping wonder by the gram
In extended ASCII jam
In the jumble and the tumble
Of the spam, spam, spam
Of the spam, spam, spam, spam
Spam, spam, spam
In the [sigma] and enigma of the spam [couldn't find a sigma character]

See the newest form of spam
Granny spam
From the friends who haven't figured out you couldn't give a damn
All the forwards that you cursed
On the day you got them first
Shall be emailed, thick and fast
Till October -- at last --
Comes around
All the tired urban legends in a hundred different guises
All the 1980s asciiart of various shapes and sizes
Still it rises, rises, rises
In a tide that soon comprises
All the lame, devoid of wit, in-
comprehensibly written
Inane garbage that can be found
Ah, the spam, spam, spam
Who'd have thought that man could cram
Without fail
Ten attachments - none worth noting -
And eleven-level quoting
In the body of an unsuspecting mail
And the viruses that came
From the friend who
Said he'd send you
An "amusing little game"
And the HTMLgram
With its glaring
Markup blaring
Out "I , therefore I am"
And the plain mail, and the chainmail -- and they're all a form of spam
Yes, they're spam
Truly spam, spam, spam, spam
Spam, spam, spam
Firmly, definition-broadeningly, spam

See the avalanche of spam
Usenet spam
Flooding through a thousand newsgroups like the water o'er a dam
All the stupid little jerks
Who insist "This really works!!!!!"
With their schemes arranged in pyramids and tiers
Who claim "Make Money Fast"
Has been legal for the lastSeveral years
Or the singularly loathed
Twerps who promise an unclothed
Britney Spears
And the sifting, sifting, sifting
Through the postings on the net
Of the harvesters who, lifting
The addresses that they get
From a hundred different places
Have a stream of databases
In a queue
And the cycle starts anew
As they spew, spew, spew, spew
Another spate of spam
For the latest hidden cam
Or some complicated scam
Like a virtual traffic jam
Still they post, post, post
While each overburdened host
Groans beneath the load of spam
Endless spam
Still they post, post, post
Till your QoS is toast
And the streaming of the spam
Of the spam, spam, spam
Has you dreaming of the spam
That they post, post, post
And you damn, damn, damn
The amounts they must have grossed
From their spam, spam, spam
From their neverending spam
From their spam, spam, spam, spam
Spam, spam, spam
From the bottomless infinitude of spam

-- Martin DeMello, Copyright 2001
(With apologies to Edgar Allan Poe )

"Life expectancy at birth is the statistic usually calculated for population groups. Life expectancy is calculated by apply age and sex-specific mortality rates from the population under study to a hypothetical birth cohort of 100,000 individuals. Life expectancy is a theoretical measure and can change for an individual with changing trends in disease frequency in the population and with individual behavioral changes. Lower life expectancy in developing countries is usually a result of high infant mortality. Once individuals reach adulthood, their life expectancy tends to be comparable across different population groups.

If you are interested in this topic, I suggest that you look into malingering. Detection of deception has been well-researched in cognitive psychology. I actually spent a few years working in a laboratory where people we researching this topic.

One of the coolest things I read about was a study where people would be hooked up so that event-related brain potentials (ERPs) were detected for malingering. In effect, your brain gives you away. For example, if you saw a video with some information and then you were asked about it, your brain does a little "hop" which can be detected with ERPs. It didn't matter how well you lied or how convincing you were, you would be detected. Supposedly, the methods works extremely well. However, you can't expect people to accept this. Would you like to have an electrode cap put on your head?

(Ah, you have to love science.)

By the way, you might want to check out these resources:

The Journal of Credibility Assessment and Witness Psychology

Forensic Psychology and Forensic Psychiatry

Polygraph Law Resource Page

This is version 0.6 of a troll HOWTO, sort of a companion piece to jsm's excellent troll FAQ. As a draft, comments and criticism are always welcome, if not appreciated :)

There are techniques used by successful trolls to elicit the maximum amount of responses from unthinking /.ers. This section is dedicated to explaining how to use these in the course of your trolls. Remember though, a great troll can break any or all of these and still be successful...

• Timing

  Because you're posting as an AC, your troll will generally be ignored in favour of posters using their accounts, and so getting in early is essential. A good guideline is to get into the first 20 posts, so that people reading the article will see the troll before it is swamped out. One way of increasing the speed with which you get your troll into play is to prepare them beforehand, and then quickly customise them for the current article. This is easier than it sounds since /. typically repeats stories with small variations and runs lots of similar stories.

  Note that this is why Jon Katz stories are pretty worthless as trolling material - by the time you've found the article and prepared a troll there's already 50+ posts on it, most of them flaming Jon Katz anyway :)

• Exposure

  Once you've got your troll in, you need people to actually read it. You also want replies - /.ers are more likely to read your troll if it starts a large thread. You also want to remember that some people have set their comment thresholds to values higher than 0 - to get the attention of these you either want to get your post moderated up (see Style, below) or get a reply which gets moderated up to 4 or 5, in which case your troll becomes visible to all.

• Accounts

  An alternative to the time-honoured tradition of AC trolling is that of creating a "troll" account. This gives you the advantage of posting at 1 rather than 0, and slashbots are more likely to take you seriously, especially if you at least sound reasonable. If you do this, try to avoid posting stuff where it is obvious you're a troll under the account - post it anoymously instead - some slightly more canny readers actually check your user info before they reply. Not many though :)

  The ultimate goal of the troll account is to secure the +1 bonus, which is currently received once you hit 26 points of Karma. To get there, employ the techniques of karma whoring that we see every day on /. and watch the karma roll in. And of course once you get the +1 bonus, the world is your oyster in terms of /. Posts made at a default of 2 hit even those people with the threshold of 2, are more likely to get moderated up even further if they are at all coherent, and people tend to lose their critical thinking abilities in the face of the +1 bonus. Milk it for all it's worth.

• Layout

  To get people reading it a troll needs to be easily readable. Make sure you break it down into easily digestible paragraphs, use HTML tags where appropriate (but always make sure you close them properly) and use whitespace appropriately.

• Size

  Generally a troll shouldn't be too short, otherwise it'll get lost in the crowd. A workable minimum is a couple of medium paragraphs. Conversely, it shouldn't be too long, or no-one will bother to read it. Keep it to a happy medium.

• Spelling

  Whilst spelling is important if you want the troll to be taken "seriously", key spelling mistakes can draw out the spelling zealots, especially if you mis-spell the name of a venerated /. hero, like Linus Torveldes or Richard Strawlman (thanks dmg). Related to this is the use of the wrong word, explaining an acronym as being something it isn't or making a word into an acronym even when it isn't.

• Subject

  The subject line needs to draw attention to your post without making it obvious that it is a troll. A simple statement of the main point of your argument can work here.

• Style

  Once you realise that most moderators don't bother to read past the first paragraph or two, you can use this fact to craft trolls that can be moderated up as "Insightful" (note that I mean this in the /. sense rather than the real-world sense). Start off fairly reasonable, making statements that are /. friendly and not being too controversial. As the troll goes on, make it more and more controversial, building it up for the coup de grace in the final paragraph.

• Linking

  As we all know, a post with links is considered "informative" by the /. crowd. Moderators love it, and they rarely check the links, so be sure to include as many as possible. And make them wrong - a link to the Perl website should instead point to the Python website instead, and vice versa. The other alternative to incorrect links is "useful" links to places like www.linux.org and www.microsoft.com i.e. places /.ers could never have found on their own :)

• Feeding

  The ideal troll requires no feeding - it runs on its own, generating flamewars between clueless /.ers for your amusement. But often a troll requires some help and so you should consider feeding it. Feeding is best reserved for people making either completely clueless responses, people making responses with holes in, or those wonderful people who write a 2000-word point-by-point rebuttal of your troll.

• Know your audience

  Always keep in mind the kind of things advocated on /. so that you can play on and against them. This is why anti-Linux, creationist, gun-loving, pro-corporation trolls work well - the vast majority of /.ers hold the opposite viewpoints. And if a few people agree with you, so much the better - it merely validates your viewpoint in the eyes of readers.

• Arrogance

  Be arrogant. You, as a troll, know that you're right. No other explanation could exist. The wronger the "fact", the more assertively you should state it. Make it clear that you are better than everyone else - you know the truth and they are just too stupid to realise it. Use plenty of sarcasm, and use "quotes" to show it to people too dumb to realise.

• Offensiveness

  Being offensive in your initial troll can be counter-productive - it causes moderators to mark you down as flamebait in general. But if you're feeding, then you can get away with calling /.ers all kinds of things. Make broad generalisations about /. readers - call them "long-haired Linux zealots", "socialist open-source bigots" or whatever. Stereotyping is encouraged - people always want to think that they're an individual, and will point this out to you given half a chance.

• Indifference

  Great for articles with a political or social bent, this kind of troll expresses complete indifference to the topic at hand, wondering who on Earth cares about it. An alternative method is to say that the topic only concerns a certain group of people - criminals, idiots, hackers (always use this instead of crackers) or whatever group you want to offend.

• Sympathy

  Appear to take the same stance as the people you're trying to troll - claim you're as much a fan of Linux as the next man, but... This way you can make all kinds of claims in the sure knowledge that you actually know what you're talking about. A great phrase to use here is "In my experience". Remember to act like all the things you're pointing out are unfortunate but true.

• The common touch

  Always accuse /.ers of being elitist. This is an easy thing to do seeing as a lot of them are. Claim that is their grandmother couldn't use it, then they are just into it to feel better than Joe Sixpack rather than "doing it for the average user". This is always great for working into anti-Linux trolls - attack command-line tools and poorly designed desktops.

• The 31337 touch

  The opposite of the above. Claim that technology or whatever is only for the elite of society and that any attempt to open it up for everyone is wrong, an attack on intellectualism and possibly even dangerous. If people were meant to understand these things then they would, and it's their fault if they're too stupid to learn.

• Contradiction

  Never be afraid to contradict yourself, even in the space of a single sentence. The phrases "I am a top programmer who codes in VB" or "I am a supporter of open source who uses NT at work and 95 at home" will be sure to get a response from some weenie smugly pointing out the contradiction. Confuse the issue more by engaging in contradiction when you are feeding - this will confuse /.ers who will then make even more stupid replies, leaving them even more wide open for response.

  Clues

  If you're feeling brave, give the reader clues that this is an obvious troll. The classic example here is dmg's stock phrase "I am often accused of trolling (whatever that is)", but also feel free to use phrases like "I have not read the article, and I don't know much about XYZ but I feel I must comment". If anyone responds to a troll with these kinds of clues in it, feel free to bask in the glow of knee-jerk /. responses.

• Denial

  If you're unlucky someone will accuse you of being a troll (surely not!) and try and ruin it for you. If you don't want it all to end there, then be sure to counter it by accusing them of being small-minded and petty, saying that it's easier for them to say it's a troll than to accept that people have different opinions. Be sure to say this in the subject line, especially if their subject was the infamous "YHBT. YHL. HAND."

• Claiming credit

  Given that /. has its community of regular trolls (hi guys!), it's only polite to publish your troll on one of the so-called "hidden" forums for all to see and admire. This way, you get to bask in the praise of other trolls, they get to contribute to your's if they want to, and you get an easy way to find the troll later on when you want to check on its progress :)

  As for when to post it, that's a matter of opinion really. You can either post it straight away or leave it will after people start biting. Remember that the troll forum is also frequented by non-trolls, and sometimes you may get a self-declared "troll-buster" try and expose you. But remember, /.ers always post before thinking, and often it doesn't matter at all.

  There is no real current forum at the moment thanks to various spammers hitting the sids, but try trolltalk, the original troll sid started by 80md and osm way back in the day. Generally all postings are done there as an AC, with your name at the end of the post. Include a link to the troll somewhere in the text, which ideally will be directly to the post and its replies - click on the #XX link in the thread to get there.

• Ending the troll

  Sometimes you just get bored with a troll, or people start posting genuinely thoughtful stuff in reply (it does happen). When this happens it might be time to own up to the troll with a helpful "YHBT. YHL. HAND." post. Sometimes people will carry on a discussion of the issue, and if you're really lucky (and it was a great troll) they will completely fail to believe you and carry on arguing. If that happens, pat yourself on the back for writing a great troll :)

• The cheap $3 crack

  Finally, when all else fails and your troll gets moderated down to (-1, Troll) within ten seconds of you posting it, the only honourable thing to do is to accuse the moderators of smoking the cheap $3 crack (again) and give up :(

1. The Maniac

   Probably the most popular kind of troll, the Maniac holds an opinion on something, and won't budge from that opinion no matter what evidence to the contrary is presented. If challenged, the Maniac will simply get more and more agitated and abusive, deriding his opponents as "idiots", "wrong-thinking", "dangerous" and "subversive". Generally the Maniac takes a position that opposes the prevalent /. beliefs, but a similar effect can be achieved by taking a typical /. viewpoint and pushing it to ridiculous extremes.

   Maniacs can be crafted for practically every article /. posts, although some are more obvious targets than others. Civil liberty articles, especially on things like censorship, DMCA, UCITA that really get /.ers riled up, are usually extremely fruitful grounds for a well-crafted maniac. The other obvious type of article is anything which could possibly involve religion, especially evolution :)

   Here are some fruitful avenues to explore:

   • The Right-Wing Maniac

     Always popular, the right-wing maniac (RWM) is a God-fearing, gun-toting, flag-waving American, and proud of it. They don't care about the rest of the world, unless it's to "prove" that America is better than everything else, and they cannot stand liberal whining over civil rights. They hate the moral decay of America and want it to revert into a nation of heterosexual, Christian whites like it was meant to be. Woe betide anyone that dares to suggest otherwise.

   • Religion

     There are two ways to approach this kind of maniac. The harder to pull off is the militant atheist, but this is quite common amongst /. posters and you would have to be very offensive to get this to work. Of course with religion trolls, the argument can go on for ever once it's started... The more common approach is the Christian fundamentalist. They are ignorant, intolerant and bigoted in the extreme. For them the Bible is the inerrant word of God revealed to man - it contains no flaws and no contradictions. Thus they are strict Creationists - mentions of evolution or cosmology will set them off on vitriolic rants. Flaming denunciations of anyone daring to contradict the "Word of God" are the way to go, and any kind of proof can always be ignored by appealing to "secular humanist brainwashing". And let's not forget, the USA is the greatest nation on Earth because it has the righteous power of Jesus Christ behind it.

   • Ideology

     Pick a philosophy, any philosophy. This troll is a troll with a cause - they have found some kind of ideological truth, and are out to expose every other philosophy as a sham. Whether it be libertarianism, objectivism, communism or capitalism, this troll will point out the obvious "flaws" in any other philosophies, whilst spouting dogma about their own. And the best thing is - you don't even need to know that much about what you're spouting - making doctrinaire mistakes will get both sides of the argument flaming you, adding to the fun.

   • Software

     This is an old favourite and crops up in many forms, covering the gamut from OS maniacs (Linux zealots, MS-apologists or embittered BSD fanatics), language maniacs (Pascal vs. C, C vs. C++, C++ vs. Java, Perl vs. Python, VB vs. everything), application maniacs(GIMP vs. Photoshop, Netscape vs. IE, vi vs. emacs) and also includes people who complain about how technology should only be for the 31337 hackers.

   • Guns

     Americans love their guns, and will always fight passionately for their Constitutionally guarenteed rights to bear arms and shoot people. Even the slightest hint of criticism of this will bring down the wrath of a thousand and one enraged gun-owners on you, so it's always a great point to work into a troll :)

2. The Expert

   The Expert is someone who is "savvy" in their particular field, and is perfectly willing to give their opinion on any topic even vauguely related to their field. The Expert is most likely to be from a field which /.ers as a rule despise - the classic example is dumb marketing guy, but try consultants, lawyers, politicians, lobbyists, executives, journalists (just think Jon Katz). With this kind of troll sweeping statements with little content are the norm, along wire dire portents of future catastrophe and dark hints of "insider knowledge".

   Some possible angles to exploit:

   • Industry knowledge

     The expert knows the computing industry from the inside - as a long-term pro, they can dispense knowledge knowing that they can "speak for the industry". Their smug self-satisfaction is bound to annoy, as is any suggestion that things aren't the way that /.ers would like it - saying "Linux requires the rock-solid guarantee of a trusted company like Microsoft" or "Apache cannot be trusted for mission-critical enterprise platforms" is guaranteed to get you denials explaining exactly why you're wrong, in excruciating detail.

   • Helpful hints

     With their tech-savvy (or law-savvy or whatever) experience, the expert is obviously the best person to point out what's wrong with things or to give out useful "factual" information. In fact this probably works best with lawyer trolls - for all that /.ers protest "IANAL", they certainly seem to think they could be, and any mistakes you make will send them rushing to prove themselves by correcting you.

3. Offtopic Trolls

   Not really a "troll" in the strict Jargon File sense of the word, but they certainly should be included here :) This category includes parodies, offtopic weirdness any all kinds of amusing stuff. Not really my area of expertise, this stuff is mainly done by gnarphlager and opensourceman. Thanks to gnarphlager for this section.

   Offtopic trolls, like any other, come in almost as many colours as an iMac, but generally not as cute. But then again, a good offtopic "troll" can affect more people than a repulsive little gumdrop on your desk, because you need to have someone SEE your desk before they can react. Simple? Moreso than even my overblown prose could indicate. Some basic examples:

   1. The serial troll

      Write a story. Keep expanding it. It doesn't matter what article you post it under, so long as it's high up. If you want people to recognize you, pick a couple themes or symbols, and carry them on throughout the story. Other alternatives include back linking or including the entire story, but adding more each time. Be funny if you want. Or if you don't feel like being funny, just be really weird. Someone will react.

   2. The random troll

      This has nothing to do with anything. Be it a stream of consciousness rant, or a description of the corner of your desk. Another favorite is a monologue, read as if spoken from any one given entity to another. The more outlandish, the better (a pair of socks talking to a mousepad, for example). If you really wanted to be artsy, work in an actual metaphor or legitimate meaning behind it, but it's not necessary.

   3. The vaguely related troll

      Start out with a comment about the article. Have a definite opinion of it. Then, after a little while, disintegrate into randomness. All roads eventually can eventually lead to cheese (yum), Natalie Portman, cannibalism, toasters, squirrels, futons, you name it. All it takes is a little bit of creativity. Oh, and feel free to use other trolls' motifs. Open source and all that ;-)

   General tips:

   • If it's funny for a fleeting moment, then it's worth posting.
   • Puns. Puns are only less vile than mimes, but it's hard to mime on /. So feel free/obligated to litter your offtopic and random bits with puns. Hurt the bastards. And if they're sick enough to laugh at them, then they'll eventually end up here ;-)
   • Obscure cultural references and injokes are always good. SOMEONE will get them eventually.
   • Several drafts of a serial or random post are common, but true elegance is being able to come up with something on the spot that still makes the top 40 posts (on a post-heavy article)

The following links contain background information useful for trolls needing quick quotes and "expert" opinions to include.

1. General purpose links
   • ddi.digital.net/~gandalf/trollfaq.html - How to deal with USENET trolls - learn your enemy :)
   • www.don-lindsay-archive.org/skeptic/arguments.html - A List Of Fallacious Arguments - Learn them and use them liberally
   • www.altairiv.demon.co.uk/troll/trollfaq.html - USENET troll HOWTO
   • www.baiting.org - Baiting.org
   • www.fieldingtravel.com/df/index.htm - Fielding's DangerFinder - A guide to what and where's dangerous
   
   
2. Religious links
   • www.godhatesamerica.com/ - God Hates America
   • www.chalcedon.edu/creed.html - The Creed of Christian Reconstruction
   • www.demonbuster.com - How to cast out your demons and do spiritual warfare
   • riceinfo.rice.edu/armadillo/Sciacademy/riggins/thi ngs.htm - Things Creationists hate
   • www.icr.org/ - Institute for Creation Research
   • www.xenu.net - Operation Clambake - The fight against Scientology on the net
   • www.hom.net/~angels/ - Citizens for the Ten Commandments
   • www.bju.edu/rcnbc.html - The difference between Catholics and Christians
   • www.geocities.com/prazske00/biblequotes.html - Bible quotes by category
   
   
3. Political/economy links
   • www.aynrand.org - The Ayn Rand Institute
   • www.reason.com - Libertarian site
   • www.freerepublic.com - Right-wing stuff
   • www.jbs.org - Excellent site for all kinds of right-wingery
   • www.dack.com/web/bullshit.html - Web economy bullshit generator
   
   
4. Crackpot science links
   • www.fixedearth.com - The Earth Is Not Moving
   • www.jir.com/index.htm - The Journal of Irreproducible Results

© spiralx, I did not write this ;)

This is version 0.6 of a troll HOWTO, sort of a companion piece to jsm's excellent troll FAQ. As a draft, comments and criticism are always welcome, if not appreciated :)

There are techniques used by successful trolls to elicit the maximum amount of responses from unthinking /.ers. This section is dedicated to explaining how to use these in the course of your trolls. Remember though, a great troll can break any or all of these and still be successful...

• Timing

  Because you're posting as an AC, your troll will generally be ignored in favour of posters using their accounts, and so getting in early is essential. A good guideline is to get into the first 20 posts, so that people reading the article will see the troll before it is swamped out. One way of increasing the speed with which you get your troll into play is to prepare them beforehand, and then quickly customise them for the current article. This is easier than it sounds since /. typically repeats stories with small variations and runs lots of similar stories.

  Note that this is why Jon Katz stories are pretty worthless as trolling material - by the time you've found the article and prepared a troll there's already 50+ posts on it, most of them flaming Jon Katz anyway :)

• Exposure

  Once you've got your troll in, you need people to actually read it. You also want replies - /.ers are more likely to read your troll if it starts a large thread. You also want to remember that some people have set their comment thresholds to values higher than 0 - to get the attention of these you either want to get your post moderated up (see Style, below) or get a reply which gets moderated up to 4 or 5, in which case your troll becomes visible to all.

• Accounts

  An alternative to the time-honoured tradition of AC trolling is that of creating a "troll" account. This gives you the advantage of posting at 1 rather than 0, and slashbots are more likely to take you seriously, especially if you at least sound reasonable. If you do this, try to avoid posting stuff where it is obvious you're a troll under the account - post it anoymously instead - some slightly more canny readers actually check your user info before they reply. Not many though :)

  The ultimate goal of the troll account is to secure the +1 bonus, which is currently received once you hit 26 points of Karma. To get there, employ the techniques of karma whoring that we see every day on /. and watch the karma roll in. And of course once you get the +1 bonus, the world is your oyster in terms of /. Posts made at a default of 2 hit even those people with the threshold of 2, are more likely to get moderated up even further if they are at all coherent, and people tend to lose their critical thinking abilities in the face of the +1 bonus. Milk it for all it's worth.

• Layout

  To get people reading it a troll needs to be easily readable. Make sure you break it down into easily digestible paragraphs, use HTML tags where appropriate (but always make sure you close them properly) and use whitespace appropriately.

• Size

  Generally a troll shouldn't be too short, otherwise it'll get lost in the crowd. A workable minimum is a couple of medium paragraphs. Conversely, it shouldn't be too long, or no-one will bother to read it. Keep it to a happy medium.

• Spelling

  Whilst spelling is important if you want the troll to be taken "seriously", key spelling mistakes can draw out the spelling zealots, especially if you mis-spell the name of a venerated /. hero, like Linus Torveldes or Richard Strawlman (thanks dmg). Related to this is the use of the wrong word, explaining an acronym as being something it isn't or making a word into an acronym even when it isn't.

• Subject

  The subject line needs to draw attention to your post without making it obvious that it is a troll. A simple statement of the main point of your argument can work here.

• Style

  Once you realise that most moderators don't bother to read past the first paragraph or two, you can use this fact to craft trolls that can be moderated up as "Insightful" (note that I mean this in the /. sense rather than the real-world sense). Start off fairly reasonable, making statements that are /. friendly and not being too controversial. As the troll goes on, make it more and more controversial, building it up for the coup de grace in the final paragraph.

• Linking

  As we all know, a post with links is considered "informative" by the /. crowd. Moderators love it, and they rarely check the links, so be sure to include as many as possible. And make them wrong - a link to the Perl website should instead point to the Python website instead, and vice versa. The other alternative to incorrect links is "useful" links to places like www.linux.org and www.microsoft.com i.e. places /.ers could never have found on their own :)

• Feeding

  The ideal troll requires no feeding - it runs on its own, generating flamewars between clueless /.ers for your amusement. But often a troll requires some help and so you should consider feeding it. Feeding is best reserved for people making either completely clueless responses, people making responses with holes in, or those wonderful people who write a 2000-word point-by-point rebuttal of your troll.

• Know your audience

  Always keep in mind the kind of things advocated on /. so that you can play on and against them. This is why anti-Linux, creationist, gun-loving, pro-corporation trolls work well - the vast majority of /.ers hold the opposite viewpoints. And if a few people agree with you, so much the better - it merely validates your viewpoint in the eyes of readers.

• Arrogance

  Be arrogant. You, as a troll, know that you're right. No other explanation could exist. The wronger the "fact", the more assertively you should state it. Make it clear that you are better than everyone else - you know the truth and they are just too stupid to realise it. Use plenty of sarcasm, and use "quotes" to show it to people too dumb to realise.

• Offensiveness

  Being offensive in your initial troll can be counter-productive - it causes moderators to mark you down as flamebait in general. But if you're feeding, then you can get away with calling /.ers all kinds of things. Make broad generalisations about /. readers - call them "long-haired Linux zealots", "socialist open-source bigots" or whatever. Stereotyping is encouraged - people always want to think that they're an individual, and will point this out to you given half a chance.

• Indifference

  Great for articles with a political or social bent, this kind of troll expresses complete indifference to the topic at hand, wondering who on Earth cares about it. An alternative method is to say that the topic only concerns a certain group of people - criminals, idiots, hackers (always use this instead of crackers) or whatever group you want to offend.

• Sympathy

  Appear to take the same stance as the people you're trying to troll - claim you're as much a fan of Linux as the next man, but... This way you can make all kinds of claims in the sure knowledge that you actually know what you're talking about. A great phrase to use here is "In my experience". Remember to act like all the things you're pointing out are unfortunate but true.

• The common touch

  Always accuse /.ers of being elitist. This is an easy thing to do seeing as a lot of them are. Claim that is their grandmother couldn't use it, then they are just into it to feel better than Joe Sixpack rather than "doing it for the average user". This is always great for working into anti-Linux trolls - attack command-line tools and poorly designed desktops.

• The 31337 touch

  The opposite of the above. Claim that technology or whatever is only for the elite of society and that any attempt to open it up for everyone is wrong, an attack on intellectualism and possibly even dangerous. If people were meant to understand these things then they would, and it's their fault if they're too stupid to learn.

• Contradiction

  Never be afraid to contradict yourself, even in the space of a single sentence. The phrases "I am a top programmer who codes in VB" or "I am a supporter of open source who uses NT at work and 95 at home" will be sure to get a response from some weenie smugly pointing out the contradiction. Confuse the issue more by engaging in contradiction when you are feeding - this will confuse /.ers who will then make even more stupid replies, leaving them even more wide open for response.

  Clues

  If you're feeling brave, give the reader clues that this is an obvious troll. The classic example here is dmg's stock phrase "I am often accused of trolling (whatever that is)", but also feel free to use phrases like "I have not read the article, and I don't know much about XYZ but I feel I must comment". If anyone responds to a troll with these kinds of clues in it, feel free to bask in the glow of knee-jerk /. responses.

• Denial

  If you're unlucky someone will accuse you of being a troll (surely not!) and try and ruin it for you. If you don't want it all to end there, then be sure to counter it by accusing them of being small-minded and petty, saying that it's easier for them to say it's a troll than to accept that people have different opinions. Be sure to say this in the subject line, especially if their subject was the infamous "YHBT. YHL. HAND."

• Claiming credit

  Given that /. has its community of regular trolls (hi guys!), it's only polite to publish your troll on one of the so-called "hidden" forums for all to see and admire. This way, you get to bask in the praise of other trolls, they get to contribute to your's if they want to, and you get an easy way to find the troll later on when you want to check on its progress :)

  As for when to post it, that's a matter of opinion really. You can either post it straight away or leave it will after people start biting. Remember that the troll forum is also frequented by non-trolls, and sometimes you may get a self-declared "troll-buster" try and expose you. But remember, /.ers always post before thinking, and often it doesn't matter at all.

  There is no real current forum at the moment thanks to various spammers hitting the sids, but try trolltalk, the original troll sid started by 80md and osm way back in the day. Generally all postings are done there as an AC, with your name at the end of the post. Include a link to the troll somewhere in the text, which ideally will be directly to the post and its replies - click on the #XX link in the thread to get there.

• Ending the troll

  Sometimes you just get bored with a troll, or people start posting genuinely thoughtful stuff in reply (it does happen). When this happens it might be time to own up to the troll with a helpful "YHBT. YHL. HAND." post. Sometimes people will carry on a discussion of the issue, and if you're really lucky (and it was a great troll) they will completely fail to believe you and carry on arguing. If that happens, pat yourself on the back for writing a great troll :)

• The cheap $3 crack

  Finally, when all else fails and your troll gets moderated down to (-1, Troll) within ten seconds of you posting it, the only honourable thing to do is to accuse the moderators of smoking the cheap $3 crack (again) and give up :(

1. The Maniac

   Probably the most popular kind of troll, the Maniac holds an opinion on something, and won't budge from that opinion no matter what evidence to the contrary is presented. If challenged, the Maniac will simply get more and more agitated and abusive, deriding his opponents as "idiots", "wrong-thinking", "dangerous" and "subversive". Generally the Maniac takes a position that opposes the prevalent /. beliefs, but a similar effect can be achieved by taking a typical /. viewpoint and pushing it to ridiculous extremes.

   Maniacs can be crafted for practically every article /. posts, although some are more obvious targets than others. Civil liberty articles, especially on things like censorship, DMCA, UCITA that really get /.ers riled up, are usually extremely fruitful grounds for a well-crafted maniac. The other obvious type of article is anything which could possibly involve religion, especially evolution :)

   Here are some fruitful avenues to explore:

   • The Right-Wing Maniac

     Always popular, the right-wing maniac (RWM) is a God-fearing, gun-toting, flag-waving American, and proud of it. They don't care about the rest of the world, unless it's to "prove" that America is better than everything else, and they cannot stand liberal whining over civil rights. They hate the moral decay of America and want it to revert into a nation of heterosexual, Christian whites like it was meant to be. Woe betide anyone that dares to suggest otherwise.

   • Religion

     There are two ways to approach this kind of maniac. The harder to pull off is the militant atheist, but this is quite common amongst /. posters and you would have to be very offensive to get this to work. Of course with religion trolls, the argument can go on for ever once it's started... The more common approach is the Christian fundamentalist. They are ignorant, intolerant and bigoted in the extreme. For them the Bible is the inerrant word of God revealed to man - it contains no flaws and no contradictions. Thus they are strict Creationists - mentions of evolution or cosmology will set them off on vitriolic rants. Flaming denunciations of anyone daring to contradict the "Word of God" are the way to go, and any kind of proof can always be ignored by appealing to "secular humanist brainwashing". And let's not forget, the USA is the greatest nation on Earth because it has the righteous power of Jesus Christ behind it.

   • Ideology

     Pick a philosophy, any philosophy. This troll is a troll with a cause - they have found some kind of ideological truth, and are out to expose every other philosophy as a sham. Whether it be libertarianism, objectivism, communism or capitalism, this troll will point out the obvious "flaws" in any other philosophies, whilst spouting dogma about their own. And the best thing is - you don't even need to know that much about what you're spouting - making doctrinaire mistakes will get both sides of the argument flaming you, adding to the fun.

   • Software

     This is an old favourite and crops up in many forms, covering the gamut from OS maniacs (Linux zealots, MS-apologists or embittered BSD fanatics), language maniacs (Pascal vs. C, C vs. C++, C++ vs. Java, Perl vs. Python, VB vs. everything), application maniacs(GIMP vs. Photoshop, Netscape vs. IE, vi vs. emacs) and also includes people who complain about how technology should only be for the 31337 hackers.

   • Guns

     Americans love their guns, and will always fight passionately for their Constitutionally guarenteed rights to bear arms and shoot people. Even the slightest hint of criticism of this will bring down the wrath of a thousand and one enraged gun-owners on you, so it's always a great point to work into a troll :)

2. The Expert

   The Expert is someone who is "savvy" in their particular field, and is perfectly willing to give their opinion on any topic even vauguely related to their field. The Expert is most likely to be from a field which /.ers as a rule despise - the classic example is dumb marketing guy, but try consultants, lawyers, politicians, lobbyists, executives, journalists (just think Jon Katz). With this kind of troll sweeping statements with little content are the norm, along wire dire portents of future catastrophe and dark hints of "insider knowledge".

   Some possible angles to exploit:

   • Industry knowledge

     The expert knows the computing industry from the inside - as a long-term pro, they can dispense knowledge knowing that they can "speak for the industry". Their smug self-satisfaction is bound to annoy, as is any suggestion that things aren't the way that /.ers would like it - saying "Linux requires the rock-solid guarantee of a trusted company like Microsoft" or "Apache cannot be trusted for mission-critical enterprise platforms" is guaranteed to get you denials explaining exactly why you're wrong, in excruciating detail.

   • Helpful hints

     With their tech-savvy (or law-savvy or whatever) experience, the expert is obviously the best person to point out what's wrong with things or to give out useful "factual" information. In fact this probably works best with lawyer trolls - for all that /.ers protest "IANAL", they certainly seem to think they could be, and any mistakes you make will send them rushing to prove themselves by correcting you.

3. Offtopic Trolls

   Not really a "troll" in the strict Jargon File sense of the word, but they certainly should be included here :) This category includes parodies, offtopic weirdness any all kinds of amusing stuff. Not really my area of expertise, this stuff is mainly done by gnarphlager and opensourceman. Thanks to gnarphlager for this section.

   Offtopic trolls, like any other, come in almost as many colours as an iMac, but generally not as cute. But then again, a good offtopic "troll" can affect more people than a repulsive little gumdrop on your desk, because you need to have someone SEE your desk before they can react. Simple? Moreso than even my overblown prose could indicate. Some basic examples:

   1. The serial troll

      Write a story. Keep expanding it. It doesn't matter what article you post it under, so long as it's high up. If you want people to recognize you, pick a couple themes or symbols, and carry them on throughout the story. Other alternatives include back linking or including the entire story, but adding more each time. Be funny if you want. Or if you don't feel like being funny, just be really weird. Someone will react.

   2. The random troll

      This has nothing to do with anything. Be it a stream of consciousness rant, or a description of the corner of your desk. Another favorite is a monologue, read as if spoken from any one given entity to another. The more outlandish, the better (a pair of socks talking to a mousepad, for example). If you really wanted to be artsy, work in an actual metaphor or legitimate meaning behind it, but it's not necessary.

   3. The vaguely related troll

      Start out with a comment about the article. Have a definite opinion of it. Then, after a little while, disintegrate into randomness. All roads eventually can eventually lead to cheese (yum), Natalie Portman, cannibalism, toasters, squirrels, futons, you name it. All it takes is a little bit of creativity. Oh, and feel free to use other trolls' motifs. Open source and all that ;-)

   General tips:

   • If it's funny for a fleeting moment, then it's worth posting.
   • Puns. Puns are only less vile than mimes, but it's hard to mime on /. So feel free/obligated to litter your offtopic and random bits with puns. Hurt the bastards. And if they're sick enough to laugh at them, then they'll eventually end up here ;-)
   • Obscure cultural references and injokes are always good. SOMEONE will get them eventually.
   • Several drafts of a serial or random post are common, but true elegance is being able to come up with something on the spot that still makes the top 40 posts (on a post-heavy article)

The following links contain background information useful for trolls needing quick quotes and "expert" opinions to include.

1. General purpose links
   • ddi.digital.net/~gandalf/trollfaq.html - How to deal with USENET trolls - learn your enemy :)
   • www.don-lindsay-archive.org/skeptic/arguments.html - A List Of Fallacious Arguments - Learn them and use them liberally
   • www.altairiv.demon.co.uk/troll/trollfaq.html - USENET troll HOWTO
   • www.baiting.org - Baiting.org
   • www.fieldingtravel.com/df/index.htm - Fielding's DangerFinder - A guide to what and where's dangerous
   
   
2. Religious links
   • www.godhatesamerica.com/ - God Hates America
   • www.chalcedon.edu/creed.html - The Creed of Christian Reconstruction
   • www.demonbuster.com - How to cast out your demons and do spiritual warfare
   • riceinfo.rice.edu/armadillo/Sciacademy/riggins/thi ngs.htm - Things Creationists hate
   • www.icr.org/ - Institute for Creation Research
   • www.xenu.net - Operation Clambake - The fight against Scientology on the net
   • www.hom.net/~angels/ - Citizens for the Ten Commandments
   • www.bju.edu/rcnbc.html - The difference between Catholics and Christians
   • www.geocities.com/prazske00/biblequotes.html - Bible quotes by category
   
   
3. Political/economy links
   • www.aynrand.org - The Ayn Rand Institute
   • www.reason.com - Libertarian site
   • www.freerepublic.com - Right-wing stuff
   • www.jbs.org - Excellent site for all kinds of right-wingery
   • www.dack.com/web/bullshit.html - Web economy bullshit generator
   
   
4. Crackpot science links
   • www.fixedearth.com - The Earth Is Not Moving
   • www.jir.com/index.htm - The Journal of Irreproducible Results

© spiralx, I did not write this ;)

This is version 0.6 of a troll HOWTO, sort of a companion piece to jsm's excellent troll FAQ. As a draft, comments and criticism are always welcome, if not appreciated :)

There are techniques used by successful trolls to elicit the maximum amount of responses from unthinking /.ers. This section is dedicated to explaining how to use these in the course of your trolls. Remember though, a great troll can break any or all of these and still be successful...

• Timing

  Because you're posting as an AC, your troll will generally be ignored in favour of posters using their accounts, and so getting in early is essential. A good guideline is to get into the first 20 posts, so that people reading the article will see the troll before it is swamped out. One way of increasing the speed with which you get your troll into play is to prepare them beforehand, and then quickly customise them for the current article. This is easier than it sounds since /. typically repeats stories with small variations and runs lots of similar stories.

  Note that this is why Jon Katz stories are pretty worthless as trolling material - by the time you've found the article and prepared a troll there's already 50+ posts on it, most of them flaming Jon Katz anyway :)

• Exposure

  Once you've got your troll in, you need people to actually read it. You also want replies - /.ers are more likely to read your troll if it starts a large thread. You also want to remember that some people have set their comment thresholds to values higher than 0 - to get the attention of these you either want to get your post moderated up (see Style, below) or get a reply which gets moderated up to 4 or 5, in which case your troll becomes visible to all.

• Accounts

  An alternative to the time-honoured tradition of AC trolling is that of creating a "troll" account. This gives you the advantage of posting at 1 rather than 0, and slashbots are more likely to take you seriously, especially if you at least sound reasonable. If you do this, try to avoid posting stuff where it is obvious you're a troll under the account - post it anoymously instead - some slightly more canny readers actually check your user info before they reply. Not many though :)

  The ultimate goal of the troll account is to secure the +1 bonus, which is currently received once you hit 26 points of Karma. To get there, employ the techniques of karma whoring that we see every day on /. and watch the karma roll in. And of course once you get the +1 bonus, the world is your oyster in terms of /. Posts made at a default of 2 hit even those people with the threshold of 2, are more likely to get moderated up even further if they are at all coherent, and people tend to lose their critical thinking abilities in the face of the +1 bonus. Milk it for all it's worth.

• Layout

  To get people reading it a troll needs to be easily readable. Make sure you break it down into easily digestible paragraphs, use HTML tags where appropriate (but always make sure you close them properly) and use whitespace appropriately.

• Size

  Generally a troll shouldn't be too short, otherwise it'll get lost in the crowd. A workable minimum is a couple of medium paragraphs. Conversely, it shouldn't be too long, or no-one will bother to read it. Keep it to a happy medium.

• Spelling

  Whilst spelling is important if you want the troll to be taken "seriously", key spelling mistakes can draw out the spelling zealots, especially if you mis-spell the name of a venerated /. hero, like Linus Torveldes or Richard Strawlman (thanks dmg). Related to this is the use of the wrong word, explaining an acronym as being something it isn't or making a word into an acronym even when it isn't.

• Subject

  The subject line needs to draw attention to your post without making it obvious that it is a troll. A simple statement of the main point of your argument can work here.

• Style

  Once you realise that most moderators don't bother to read past the first paragraph or two, you can use this fact to craft trolls that can be moderated up as "Insightful" (note that I mean this in the /. sense rather than the real-world sense). Start off fairly reasonable, making statements that are /. friendly and not being too controversial. As the troll goes on, make it more and more controversial, building it up for the coup de grace in the final paragraph.

• Linking

  As we all know, a post with links is considered "informative" by the /. crowd. Moderators love it, and they rarely check the links, so be sure to include as many as possible. And make them wrong - a link to the Perl website should instead point to the Python website instead, and vice versa. The other alternative to incorrect links is "useful" links to places like www.linux.org and www.microsoft.com i.e. places /.ers could never have found on their own :)

• Feeding

  The ideal troll requires no feeding - it runs on its own, generating flamewars between clueless /.ers for your amusement. But often a troll requires some help and so you should consider feeding it. Feeding is best reserved for people making either completely clueless responses, people making responses with holes in, or those wonderful people who write a 2000-word point-by-point rebuttal of your troll.

• Know your audience

  Always keep in mind the kind of things advocated on /. so that you can play on and against them. This is why anti-Linux, creationist, gun-loving, pro-corporation trolls work well - the vast majority of /.ers hold the opposite viewpoints. And if a few people agree with you, so much the better - it merely validates your viewpoint in the eyes of readers.

• Arrogance

  Be arrogant. You, as a troll, know that you're right. No other explanation could exist. The wronger the "fact", the more assertively you should state it. Make it clear that you are better than everyone else - you know the truth and they are just too stupid to realise it. Use plenty of sarcasm, and use "quotes" to show it to people too dumb to realise.

• Offensiveness

  Being offensive in your initial troll can be counter-productive - it causes moderators to mark you down as flamebait in general. But if you're feeding, then you can get away with calling /.ers all kinds of things. Make broad generalisations about /. readers - call them "long-haired Linux zealots", "socialist open-source bigots" or whatever. Stereotyping is encouraged - people always want to think that they're an individual, and will point this out to you given half a chance.

• Indifference

  Great for articles with a political or social bent, this kind of troll expresses complete indifference to the topic at hand, wondering who on Earth cares about it. An alternative method is to say that the topic only concerns a certain group of people - criminals, idiots, hackers (always use this instead of crackers) or whatever group you want to offend.

• Sympathy

  Appear to take the same stance as the people you're trying to troll - claim you're as much a fan of Linux as the next man, but... This way you can make all kinds of claims in the sure knowledge that you actually know what you're talking about. A great phrase to use here is "In my experience". Remember to act like all the things you're pointing out are unfortunate but true.

• The common touch

  Always accuse /.ers of being elitist. This is an easy thing to do seeing as a lot of them are. Claim that is their grandmother couldn't use it, then they are just into it to feel better than Joe Sixpack rather than "doing it for the average user". This is always great for working into anti-Linux trolls - attack command-line tools and poorly designed desktops.

• The 31337 touch

  The opposite of the above. Claim that technology or whatever is only for the elite of society and that any attempt to open it up for everyone is wrong, an attack on intellectualism and possibly even dangerous. If people were meant to understand these things then they would, and it's their fault if they're too stupid to learn.

• Contradiction

  Never be afraid to contradict yourself, even in the space of a single sentence. The phrases "I am a top programmer who codes in VB" or "I am a supporter of open source who uses NT at work and 95 at home" will be sure to get a response from some weenie smugly pointing out the contradiction. Confuse the issue more by engaging in contradiction when you are feeding - this will confuse /.ers who will then make even more stupid replies, leaving them even more wide open for response.

  Clues

  If you're feeling brave, give the reader clues that this is an obvious troll. The classic example here is dmg's stock phrase "I am often accused of trolling (whatever that is)", but also feel free to use phrases like "I have not read the article, and I don't know much about XYZ but I feel I must comment". If anyone responds to a troll with these kinds of clues in it, feel free to bask in the glow of knee-jerk /. responses.

• Denial

  If you're unlucky someone will accuse you of being a troll (surely not!) and try and ruin it for you. If you don't want it all to end there, then be sure to counter it by accusing them of being small-minded and petty, saying that it's easier for them to say it's a troll than to accept that people have different opinions. Be sure to say this in the subject line, especially if their subject was the infamous "YHBT. YHL. HAND."

• Claiming credit

  Given that /. has its community of regular trolls (hi guys!), it's only polite to publish your troll on one of the so-called "hidden" forums for all to see and admire. This way, you get to bask in the praise of other trolls, they get to contribute to your's if they want to, and you get an easy way to find the troll later on when you want to check on its progress :)

  As for when to post it, that's a matter of opinion really. You can either post it straight away or leave it will after people start biting. Remember that the troll forum is also frequented by non-trolls, and sometimes you may get a self-declared "troll-buster" try and expose you. But remember, /.ers always post before thinking, and often it doesn't matter at all.

  There is no real current forum at the moment thanks to various spammers hitting the sids, but try trolltalk, the original troll sid started by 80md and osm way back in the day. Generally all postings are done there as an AC, with your name at the end of the post. Include a link to the troll somewhere in the text, which ideally will be directly to the post and its replies - click on the #XX link in the thread to get there.

• Ending the troll

  Sometimes you just get bored with a troll, or people start posting genuinely thoughtful stuff in reply (it does happen). When this happens it might be time to own up to the troll with a helpful "YHBT. YHL. HAND." post. Sometimes people will carry on a discussion of the issue, and if you're really lucky (and it was a great troll) they will completely fail to believe you and carry on arguing. If that happens, pat yourself on the back for writing a great troll :)

• The cheap $3 crack

  Finally, when all else fails and your troll gets moderated down to (-1, Troll) within ten seconds of you posting it, the only honourable thing to do is to accuse the moderators of smoking the cheap $3 crack (again) and give up :(

1. The Maniac

   Probably the most popular kind of troll, the Maniac holds an opinion on something, and won't budge from that opinion no matter what evidence to the contrary is presented. If challenged, the Maniac will simply get more and more agitated and abusive, deriding his opponents as "idiots", "wrong-thinking", "dangerous" and "subversive". Generally the Maniac takes a position that opposes the prevalent /. beliefs, but a similar effect can be achieved by taking a typical /. viewpoint and pushing it to ridiculous extremes.

   Maniacs can be crafted for practically every article /. posts, although some are more obvious targets than others. Civil liberty articles, especially on things like censorship, DMCA, UCITA that really get /.ers riled up, are usually extremely fruitful grounds for a well-crafted maniac. The other obvious type of article is anything which could possibly involve religion, especially evolution :)

   Here are some fruitful avenues to explore:

   • The Right-Wing Maniac

     Always popular, the right-wing maniac (RWM) is a God-fearing, gun-toting, flag-waving American, and proud of it. They don't care about the rest of the world, unless it's to "prove" that America is better than everything else, and they cannot stand liberal whining over civil rights. They hate the moral decay of America and want it to revert into a nation of heterosexual, Christian whites like it was meant to be. Woe betide anyone that dares to suggest otherwise.

   • Religion

     There are two ways to approach this kind of maniac. The harder to pull off is the militant atheist, but this is quite common amongst /. posters and you would have to be very offensive to get this to work. Of course with religion trolls, the argument can go on for ever once it's started... The more common approach is the Christian fundamentalist. They are ignorant, intolerant and bigoted in the extreme. For them the Bible is the inerrant word of God revealed to man - it contains no flaws and no contradictions. Thus they are strict Creationists - mentions of evolution or cosmology will set them off on vitriolic rants. Flaming denunciations of anyone daring to contradict the "Word of God" are the way to go, and any kind of proof can always be ignored by appealing to "secular humanist brainwashing". And let's not forget, the USA is the greatest nation on Earth because it has the righteous power of Jesus Christ behind it.

   • Ideology

     Pick a philosophy, any philosophy. This troll is a troll with a cause - they have found some kind of ideological truth, and are out to expose every other philosophy as a sham. Whether it be libertarianism, objectivism, communism or capitalism, this troll will point out the obvious "flaws" in any other philosophies, whilst spouting dogma about their own. And the best thing is - you don't even need to know that much about what you're spouting - making doctrinaire mistakes will get both sides of the argument flaming you, adding to the fun.

   • Software

     This is an old favourite and crops up in many forms, covering the gamut from OS maniacs (Linux zealots, MS-apologists or embittered BSD fanatics), language maniacs (Pascal vs. C, C vs. C++, C++ vs. Java, Perl vs. Python, VB vs. everything), application maniacs(GIMP vs. Photoshop, Netscape vs. IE, vi vs. emacs) and also includes people who complain about how technology should only be for the 31337 hackers.

   • Guns

     Americans love their guns, and will always fight passionately for their Constitutionally guarenteed rights to bear arms and shoot people. Even the slightest hint of criticism of this will bring down the wrath of a thousand and one enraged gun-owners on you, so it's always a great point to work into a troll :)

2. The Expert

   The Expert is someone who is "savvy" in their particular field, and is perfectly willing to give their opinion on any topic even vauguely related to their field. The Expert is most likely to be from a field which /.ers as a rule despise - the classic example is dumb marketing guy, but try consultants, lawyers, politicians, lobbyists, executives, journalists (just think Jon Katz). With this kind of troll sweeping statements with little content are the norm, along wire dire portents of future catastrophe and dark hints of "insider knowledge".

   Some possible angles to exploit:

   • Industry knowledge

     The expert knows the computing industry from the inside - as a long-term pro, they can dispense knowledge knowing that they can "speak for the industry". Their smug self-satisfaction is bound to annoy, as is any suggestion that things aren't the way that /.ers would like it - saying "Linux requires the rock-solid guarantee of a trusted company like Microsoft" or "Apache cannot be trusted for mission-critical enterprise platforms" is guaranteed to get you denials explaining exactly why you're wrong, in excruciating detail.

   • Helpful hints

     With their tech-savvy (or law-savvy or whatever) experience, the expert is obviously the best person to point out what's wrong with things or to give out useful "factual" information. In fact this probably works best with lawyer trolls - for all that /.ers protest "IANAL", they certainly seem to think they could be, and any mistakes you make will send them rushing to prove themselves by correcting you.

3. Offtopic Trolls

   Not really a "troll" in the strict Jargon File sense of the word, but they certainly should be included here :) This category includes parodies, offtopic weirdness any all kinds of amusing stuff. Not really my area of expertise, this stuff is mainly done by gnarphlager and opensourceman. Thanks to gnarphlager for this section.

   Offtopic trolls, like any other, come in almost as many colours as an iMac, but generally not as cute. But then again, a good offtopic "troll" can affect more people than a repulsive little gumdrop on your desk, because you need to have someone SEE your desk before they can react. Simple? Moreso than even my overblown prose could indicate. Some basic examples:

   1. The serial troll

      Write a story. Keep expanding it. It doesn't matter what article you post it under, so long as it's high up. If you want people to recognize you, pick a couple themes or symbols, and carry them on throughout the story. Other alternatives include back linking or including the entire story, but adding more each time. Be funny if you want. Or if you don't feel like being funny, just be really weird. Someone will react.

   2. The random troll

      This has nothing to do with anything. Be it a stream of consciousness rant, or a description of the corner of your desk. Another favorite is a monologue, read as if spoken from any one given entity to another. The more outlandish, the better (a pair of socks talking to a mousepad, for example). If you really wanted to be artsy, work in an actual metaphor or legitimate meaning behind it, but it's not necessary.

   3. The vaguely related troll

      Start out with a comment about the article. Have a definite opinion of it. Then, after a little while, disintegrate into randomness. All roads eventually can eventually lead to cheese (yum), Natalie Portman, cannibalism, toasters, squirrels, futons, you name it. All it takes is a little bit of creativity. Oh, and feel free to use other trolls' motifs. Open source and all that ;-)

   General tips:

   • If it's funny for a fleeting moment, then it's worth posting.
   • Puns. Puns are only less vile than mimes, but it's hard to mime on /. So feel free/obligated to litter your offtopic and random bits with puns. Hurt the bastards. And if they're sick enough to laugh at them, then they'll eventually end up here ;-)
   • Obscure cultural references and injokes are always good. SOMEONE will get them eventually.
   • Several drafts of a serial or random post are common, but true elegance is being able to come up with something on the spot that still makes the top 40 posts (on a post-heavy article)

The following links contain background information useful for trolls needing quick quotes and "expert" opinions to include.

1. General purpose links
   • ddi.digital.net/~gandalf/trollfaq.html - How to deal with USENET trolls - learn your enemy :)
   • www.don-lindsay-archive.org/skeptic/arguments.html - A List Of Fallacious Arguments - Learn them and use them liberally
   • www.altairiv.demon.co.uk/troll/trollfaq.html - USENET troll HOWTO
   • www.baiting.org - Baiting.org
   • www.fieldingtravel.com/df/index.htm - Fielding's DangerFinder - A guide to what and where's dangerous
   
   
2. Religious links
   • www.godhatesamerica.com/ - God Hates America
   • www.chalcedon.edu/creed.html - The Creed of Christian Reconstruction
   • www.demonbuster.com - How to cast out your demons and do spiritual warfare
   • riceinfo.rice.edu/armadillo/Sciacademy/riggins/thi ngs.htm - Things Creationists hate
   • www.icr.org/ - Institute for Creation Research
   • www.xenu.net - Operation Clambake - The fight against Scientology on the net
   • www.hom.net/~angels/ - Citizens for the Ten Commandments
   • www.bju.edu/rcnbc.html - The difference between Catholics and Christians
   • www.geocities.com/prazske00/biblequotes.html - Bible quotes by category
   
   
3. Political/economy links
   • www.aynrand.org - The Ayn Rand Institute
   • www.reason.com - Libertarian site
   • www.freerepublic.com - Right-wing stuff
   • www.jbs.org - Excellent site for all kinds of right-wingery
   • www.dack.com/web/bullshit.html - Web economy bullshit generator
   
   
4. Crackpot science links
   • www.fixedearth.com - The Earth Is Not Moving
   • www.jir.com/index.htm - The Journal of Irreproducible Results

© spiralx, I did not write this ;)

Too bad the link to the bill is already broken, I would have liked to have read it.

OK I did a search and found a PDF copy of the bill HERE. Also found a site to organize support for the bill, it has a form to send your representative an email. Since Cannon is mine, I guess I'm already OK on that one. However, I have been pretty unhappy on his stance on several issues in the past, hopefully he won't drop the ball on this one under the intense politial pressure of the RIAA.

You couldn't be further from the truth. Someone's already mentioned CiteSeer. I've read and downloaded hundreds of papers from there. Google is great for tracking down papers, too.

Another nice resource is library.readscheme.org. It's Scheme-specific, but Scheme is the root of much research about programming languages and the underlying concepts - it pretty much spawned the field of functional programming.

The biggest barrier to entry for this sort of stuff is your own existing knowledge. There's no pill you can take to pick it all up overnight. You have to work hard at it. This is the real reason to go to a real universities - not to learn how to program in the language du jour, but to learn about what some very smart people have already figured out over decades, centuries, millenia, and to learn how to think like those people.

There aren't many shortcuts here. It doesn't help to be told that there's a simple solution to the problem you're working on, if it involves a network of deep concepts you've never heard of and are totally unfamiliar with. To take some examples from functional programming: closures, continuations, continuation passing style, fold operators, polymorphic type inference... If you don't know what all those things mean, and can't use them in your code, you're unnecessarily limiting yourself and denying yourself leverage that can help get big, complicated things done more quickly, with less fuss.

One way to start out is to learn some advanced languages. Scheme is a good starting point because there's so much tutorial literature for it. You can pick up the computer science concepts as you go along. Read Structure and Interpretation of Computer Programs (SICP) and How to Design Programs (HTDP). Join the ACM. There's so much stuff out there, go look for it, and apply yourself!

The problem with hierarchical file systems is that we have to choose one of them. I would love to see a storage system where we can use both ways _at the same time_. A system that groups file depending on relationships they have. Such that 'ls /etc' gives me all config files for all apps, and 'ls /usr/local/mutt' shows me all mutt-related files, including it's config file(s). I have no idea how to implement such a beast

A good many years back, I used userfs and Linux-1.3.47 to hack up a file system for managing packages. This was for a course project in my undergrad sophomore year, six years ago. Semantics were nice: ls /usr/bin did the usual thing, ls /usr/.emacs/bin showed emacs binaries, cd /.emacs switched you to a "view" of the filesystem restricted to emacs files, and all such nifty stuff. These ".emacs" type directories were internally generated by the kernel, and were invisible when you normally said "ls". It rocked the pants off slackware's /var/adm/packages based manager, and sometimes, I think, off rpm too, maybe.

We learnt some valuable lessons, especially applicable to developers of MOM and similar systems:

On the long run, it was systematic, and yet cumbersome to use. Suppose you cd /.emacs/usr/share/docs; and then you want to switch to docs of vim, and you had to go all the way down. This was fixable in theory.. and would have been worth it too..

We only grazed the issues modification and upgrade. The idea was to cd /.emacs and tar -zxvf emacs-upgrade.tar.gz. Dependencies can be a bitch.

Lastly, it (automatically) supported one nifty feature, that of cd /.emacs; tar zcvf ~/emacs.tar.gz *. This sort of thing, with added semantics like tar options to avoid .o file etc. can be marvellous for developers, compared to what's there now.

SO I think there's potential in this direction, for stuff inconceivable from user space.

I'd love to be contacted with ideas/suggestions/questions/whatever, or if you want me to dig up the code or documentation.

The problem with hierarchical file systems is that we have to choose one of them. I would love to see a storage system where we can use both ways _at the same time_. A system that groups file depending on relationships they have. Such that 'ls /etc' gives me all config files for all apps, and 'ls /usr/local/mutt' shows me all mutt-related files, including it's config file(s). I have no idea how to implement such a beast

A good many years back, I used userfs and Linux-1.3.47 to hack up a file system for managing packages. This was for a course project in my undergrad sophomore year, six years ago. Semantics were nice: ls /usr/bin did the usual thing, ls /usr/.emacs/bin showed emacs binaries, cd /.emacs switched you to a "view" of the filesystem restricted to emacs files, and all such nifty stuff. These ".emacs" type directories were internally generated by the kernel, and were invisible when you normally said "ls". It rocked the pants off slackware's /var/adm/packages based manager, and sometimes, I think, off rpm too, maybe.

We learnt some valuable lessons, especially applicable to developers of MOM and similar systems:

On the long run, it was systematic, and yet cumbersome to use. Suppose you cd /.emacs/usr/share/docs; and then you want to switch to docs of vim, and you had to go all the way down. This was fixable in theory.. and would have been worth it too..

We only grazed the issues modification and upgrade. The idea was to cd /.emacs and tar -zxvf emacs-upgrade.tar.gz. Dependencies can be a bitch.

Lastly, it (automatically) supported one nifty feature, that of cd /.emacs; tar zcvf ~/emacs.tar.gz *. This sort of thing, with added semantics like tar options to avoid .o file etc. can be marvellous for developers, compared to what's there now.

SO I think there's potential in this direction, for stuff inconceivable from user space.

I'd love to be contacted with ideas/suggestions/questions/whatever, or if you want me to dig up the code or documentation.

Some time ago I came across the following letter by Henry baker regarding relational databases. It made interesting reading.

Perhaps there is an element of 'when your only tool is a hammer, everything is a nail.' to relational databases. They are certainly so pervasive now that any idea of using something different would be seen as taking a HUGE risk.

A group of AT&T researchers broke WEP security (even the 128 bit version). See paper here. They recommend treating 802.11 connections as open and using things like SSL and SSH to protect sensitive data.

So it seems that my biggest problems don't lie with LISP at all. I may find myself a LISP convert yet! Perhaps solving criticism #1 (above) may facilitate that. :)

Here @ NEU, some professors are part of 'TeachScheme', which is an effort to push Scheme into CS curricula. They have actually put togeather a scheme implementation, DrScheme, which provides an excellent interactive environment for writing and learning scheme http://www.cs.rice.edu/CS/PLT/packages/drscheme/ Oh, and it's GPL too. runs on Mac/Windows/linux.

While we're discussing Java IDEs, you might want to look at DrJava, a graphical IDE in development at Rice University. It's the only Java IDE I've ever heard of that has a read-eval-print loop built in (that is, a little prompt where you can type in Java expressions and see the results immediately), and it looks like it's modelled after another Rice software product, DrScheme. Though it's limited now, it looks like DrJava aims to be for Java what DrScheme is for Scheme, which would be cool.

• Scientific discovery -- the manned space program is fairly spotty on this. Peer review of scientific proposals has been criticized at JSC (the 'manned spaceflight center') as being inadequate or absent. Papers published in peer-reviewed journals are relatively few, considering the billions of dollars spent. Is it unfair to expect some results in exchange for the money spent? I think so. Contrast this with other space research such as Hubble or the Very Large Array / Very Long Baseline Interferometer. Those facilities have yielded large numbers of papers. Sure, we can quibble over whether the quantity or the quality of the science is important, but ultimately there has to be some quantity.
  
• Inspiration -- Some argue that you can't put a price tag on inspiration, and that Astronauts and Cosmonauts inspire children "of all ages". Frankly, I just don't see the interest. Maybe if we put J.Lo and Kid Rock up on the Station this would change. We've seen a huge upsurge in interest in careers at FBI & CIA recently -- contrast this with the exodus at NASA.
  

So what do I propose for the manned space program? Drastically increase research into advanced transportation technologies:

• Propulsion -- e.g. Franklin Chang-Diaz's VASIMR engine, which will permit faster trips to Mars.
  
• Space tethers -- to provide artificial gravitational acceleration, to offset bone demineralization and muscular atrophy.
  
• Access to space -- the Space Launch Initiative might be OK, but we need to make sure it does not hinder commercial development, as previous initiatives and policies have.
  

Now it's well more than half of my friend's worst-case estimate later. We have nothing approaching any of those things. What we have is exactly one thing, C 60, also called buckminsterfullerene. It's a very interesting thing, but it's a material, not a machine. Its co-inventor, Dr. Richard E. Smalley, explained in the Sept. 2001 Scientific American that the Drexler assembler is and always will be impossible, because molecules are not tinkertoys that you can put together an atom at a time.

In his 1999 Senate statement, Dr. Smalley said this about potential natural security ramifications of nanotechnology research:

National Security. The Department of Defense recognized the importance of nanostructures over a decade ago and has played a significant role in nurturing the field. Critical defense applications include: (a) Continued information dominance, identified as an important capability for the military, will depend on U.S. nanotechnology. (b) Nanostructured electronics will provide more sophisticated virtual reality systems that enable affordable, effective training. (c) Reduction in military manpower must be compensated by the increased use of nanostructure-enhanced automation and robotics, both of which will benefit from nanostructures. The use of uninhabited combat vehicles is desired, both to reduce risk to human life as well as to improve vehicle performance. For example, several thousand pounds could be stripped from a pilotless fighter aircraft, resulting in longer missions. In addition, the fighter agility could be dramatically improved without the necessity to limit g-forces on the pilot, increasing its combat effectiveness. (d) Nanostructured materials hold the promise for the high performance (lighter, stronger) needed in military platforms while simultaneously providing diminished failure rates and lower life-cycle costs. (e) Advances in medicine and health enabled by nanoscience will provide badly needed chemical/biological/nuclear sensing, protection and improvements in casualty care. (f) Changes are also possible in the design and weight reduction of nuclear weapons and systems used in non-proliferation.

As you can see, it promises some incremental advances, but no basic revolutions -- certainly nothing on the level of the atomic bomb. Stronger armor, lighter planes, faster computers, smaller missiles, absolutely. But hordes of nanobattlebots? Get real.

The Drexler revolution has fallen flat on its face. We do not yet have even a semi-autonomous microbot, much less any kind of nanobot. Even at the microscale it turns out the laws of mechanics are too different from the mesoscale to allow for something as standard as a gear, and the nanoscale is much more different than that. We do not have anything vaguely resembling an assembler, and chemists say that the assembler will always be impossible.

Yet for some reason people are still concerned with these fantasies. It's just bad science fiction, like warp drives and human-animal hybrids. It's not important. We will have nanotechnology but it will be far more modest and less dangerous than the whacked-out speculations of fake futurists. Start dealing with the technology issues we really do face, like cloning, nuclear proliferation, and social monitoring. They're important. Drexler and his cult are not.

Tim

CFS and PAST are P2P readonly file systems a la Napster/Gnutella/Freenet. Both had papers in this year's SOSP. Both are based on log(N) P2P overlay routing/lookup substrates.

OceanStore seeks to be a more general (writable) global storage system.

And several P2P conferences have formed and will continue to form.

Some of these projects have been going on for years. So you shouldn't buy the "Academic networking/CS researchers are a bunch of P2P haters" line without a few grains of your favorite seasoning.

Check out DrScheme from the PLT group. It's "an interactive, integrated, graphical programming environment for the Scheme programming language". It's cross-platform, released under the GPL, and includes cross-platform GUI support (*nix & Windows), a comprehensive help system, a bunch of useful libraries for graphics, Internet, COM access on Windows, etc., as well as some useful applications like a web server, web browser, Gtk interface, a graphical IMAP mail client, and some graphical games.

The underlying Scheme implementation, known as MzScheme, includes a fast interpreter as well as a compiler that can compile to bytecode or native code.

• US National Labs rotating Java model (doesn't show the bonds though).
• loads of static models at Rice.edu.

They were probably hoping to follow the success of photo sticker machines in Japan.

I've become fairly interested lately in using Scheme (probably mzscheme) and the SXML package as a way to do arbitrary XML translations in my free time (if I had any).

From the looks of it, the ability to create a reflexive mapping between an arbitrary XML document and an interpretable programming language is too powerful to be ignored.

Do you think that in the future one of the primary roles of Scheme/Lisp is going to be in manipulation of XML documents, or is this going to be relegated as an academic curiostiy while the world struggles through parsing XML in Java?

This seems to be a pretty good collection of cheat sheets:
[RICE.EDU]

Interesting question. The BEC is characterized by the total number of particles (atoms) within. Call it N. If the constituent atoms are radioactive, and one waits for decay products of a single radioactive decay to be detected in an external detector, then one will find an N-1 atom condensate, plus one set of decay products. Which atom decayed? Atoms (of the same isotope of the same element) in their ground (lowest-energy) states are indistinguishable entities, even in non-BEC systems (ever try to tell two electrons or two protons apart? same works for assemblages of same :-). It so happens that this indistinguishabilty has few experimental consequences at normal temperatures, but more profound consequences at very low temperatures. So one can't say which atom decayed- the question is ill defined.

By the way, researchers at Rice University (Randall G. Hulet et al.) made a condensate before Wolfgang Ketterle's group at MIT. MIT was third. Wolfgang is a great phycisist and gives a spectacular talk, but I bet the Rice people are feeling a bit left out about now, for good reason.