Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
The Almighty Buck

Journal How2Troll's Journal: Lesson #001: The "PROFIT" method. 1

PREPARE FOR THE HOW2TROLL TROLLING WORKSHOP
Dedicated to teaching quality Trolling skillz

STEP 1 : Pick a story and search through for a highly-rated or otherwise prominent comment in which someone uses a nubmered list. For example, you want to find something like this:

EXAMPLE:

  1. Blah!
  2. Blah!
  3. Blah!

For example, I selected this post [slashdot.org] as a prime target. There are only a few things to keep in mind: pick an active story and a comment that'll be seen by a lot of people as the target of your troll. The comment MUST contain a numbered list, similar to the above, although the exact style of numbering can vary. Also, try to pick a comment that hasn't already been trolled this way. Every comment with a numbered list will eventually get hit, so you want to be quick.

STEP 2 : Take careful note of the method of numbering that your target post is using. It really doesn't matter, as long as it's numbered. For example, in this post I use text like "STEP 1", "STEP 2", etc. Note this carefully. This method of trolling makes the most sense when the list is a list of ordered steps (such as this vary document you are reading), BUT if the numbered list is something different, such as "REASON 1:", "REASON 2:", etc., hit it anyway! Your troll will be more esoetric and non-sequitur, but all the better: trolling doesn't always HAVE to make sense. Sometimes it's fun to confuse people.

STEP 3 : Now you'll put the information gained from step 2 to good use, as you attack the target you selected. This is where it gets complicated, so pay attention. This is easiest to explain with a couple of examples. Let's say your target looks like this:

TARGET POST:

  • 1. I am a Slashbot!
  • 2. Gosh, I hope I don't get trolled!
  • 3. Blah blah blah, whore for karma!
  • 4. In conclusion, I'm SO smart!

Now, to pull off your masterful act of trollage, you'll want to sneak in, post a reply, and do this:

TROLL REPLY:

  • 4. ???
  • 5. PROFIT!

Let's say that the post you're replying to is a bit more complex:

TARGET POST:
Reasons Linix is so great!
*REASON 1: My allowance won't cover expensive software.
*REASON 2: Completely off-topic rant about Microsoft.
*REASON 3: I love Linix!!

Now you want to come in and do this:

TROLL REPLY:
*REASON 4: ???
*REASON 5: PROFIT!

Note what I did there: I emulated the exact style of his numbered list, and then added to it in order to cleverly troll him. THAT is the key. If he numbers his list using bold, use bold. If your target uses all caps, use all caps. If he uses Roman Numerals, use Roman Numerals (hint: I II III IV V VI VII VII IX X, then everything repeats from there), etc. Make YOUR list seem like an naturally-flowing conclusion to your TARGET's list. Then give him HELL! Here's the general key:

TARGET POST:
1. Blah!
2. Blah!
3. Blah!
...
X. Blah!

TROLL REPLY
X+1. ???
X+2. PROFIT!

I know it gets complicated when you throw in the algebra, but you should be able to do it. Keep track of the numbers on a piece of paper if you have to. It's VARY difficult, but once you try it out, you'll get the hang of it. It's an aquired skill that can only be improved through hard work and practice. So get out there and troll!

Here's a summary:

STEP 1 : Pick your target (active, contains numbered list)
STEP 2 : Gather information (style of the numbered list)
STEP 3 : Nail the target by adding on to his own list!
STEP 4 : ???
STEP 5 : PROFIT!

See, I even did it to my own damn list! That's how easy it is once you become a master at this discipline of trolling! Good luck, young Jedi!!! Go out and troll the world, you motherfucking cuntrag bitches!!!

This discussion has been archived. No new comments can be posted.

Lesson #001: The "PROFIT" method.

Comments Filter:

Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (5) All right, who's the wiseguy who stuck this trigraph stuff in here?

Working...