The Anti-Linux-IPO Howto

Mike writes "The Anti-Linux-IPO Howto, it's pretty funny. Want to write an article that is Anti-Linux or an Anti-IPO article with little thought and research? Well, then The Anti-Linux-IPO Howto is for you." One of the funniest things I've read in weeks.

Comments

Sad but True

[irix]

Very funny :)

Unfortunately, was obviously actually used by many clueless morons, including some unapologetic idiots at who write for Slashdot's new owners. :(

I'm sure I'll be moderated down by the new world order.

A mini How-to

[fable2112]

This is a mini-How-to for how to flame a /. article:

It helps if the subject line doesn't contain the actual flame. That way, you're less likely to be noticed and marked down by the moderators. Be subtle about this (but ONLY this) part of the flame.

Suggested titles include:

1. If I remember right:
2. Go ahead and flame me, but
3. I disagree, and this is why...
4. No!
5. I don't get it.

Once you're in the body of the message, tell everyone why the article sucks.

"I can't believe you posted this. It sucks, because (use one or more):

1. It's NOT news for nerds!
2. It confuses hackers with crackers.
3. It glorifies cracking/cracking tools.
4. It's a childish attempt at humor.
5. It makes fun of something that is Sacred to Geeks (Star Wars, etc.)
6. It is actively critical of something that is Sacred to Geeks.
7. We've heard way too much about this topic as is; can't you talk about something else?
8. It's knee-jerk liberalism.
9. It's knee-jerk libertarianism.
10. It's full of typos.
11. Andover.net obviously made you post it.
12. You just want to see your name in print!
13. No one CARES. So shut up."

Rant and rave a bit more, and then conclude with:

1. Slashdot is really starting to suck. Remember the good old days?
2. Now I remember why I hate the media. ALL of the media.
3. Fire Jon Katz!
4. I can't believe you people are so clueless.

*grin* (Not that I'm advocating any of the above, mind you ...)