Announcement

GOOGLE CHROME IS A BOTNET? GOOGLE CHROME IS A BOTNET? GOOGLE CHROME IS A BOTNET? GOOGLE CHROME IS A BOTNET? GOOGLE CHROME IS A BOTNET? GOOGLE CHROME IS A BOTNET? GOOGLE CHROME IS A BOTNET? GOOGLE CHROME IS A BOTNET? WE LIVE INSIDE A DREAM. GOOGLE CHROME IS A BOTNET? GOOGLE CHROME IS A BOTNET? GOOGLE CHROME IS A BOTNET? GOOGLE CHROME IS A BOTNET? GOOGLE CHROME IS A BOTNET? GOOGLE CHROME IS A BOTNET? GOOGLE CHROME IS A BOTNET? NO MORE SPAM
FRIENDLY REMINDER THAT THE FORUMS ARE DEAD AND THAT THE LIFE OF THE PARTY CURRENTLY RESIDES IN #FAIL #EEFORUMSANARCHY #EEFORUMS #hi ON RIZON.

YO RIZON #HI
it's closing time you don't have to go home but you can't stay here

Advertisement

»  » 

Pages: 1

#1 2014-03-26 15:56:18

colon
"Furry"
From: 4444
Registered: 2011-06-25
Posts: 5,109
Fails: 3
Website

how to write a how to topic: a step by step guide

1: Type 'How to' in the subject box
2: Decide what to tell people how to do
3: Type it
4: Type instructions in list form in message box
5: kablam that's a how-to

what the ****

Offline

#2 2014-03-26 18:31:29

scienceguyz
VIF
Registered: 2012-03-04
Posts: 1,791
Fails: 114

Re: how to write a how to topic: a step by step guide

This is so meta right now. It's so meta, even this acronym.

No longer part of Fail. Sorry.

Offline

#3 2014-03-26 19:12:28

colon
"Furry"
From: 4444
Registered: 2011-06-25
Posts: 5,109
Fails: 3
Website

Re: how to write a how to topic: a step by step guide

much meta

very acronym

                                      so wow

what the ****

Offline

#4 2014-03-27 07:27:05

Different55
The Beanmaker
Registered: 2011-05-18
Posts: 9,143
Fails: 0

Re: how to write a how to topic: a step by step guide

10/10 would be informed by

Jet fuel can't make dank memes.

Offline

#5 2014-03-27 11:36:59

colon
"Furry"
From: 4444
Registered: 2011-06-25
Posts: 5,109
Fails: 3
Website

Re: how to write a how to topic: a step by step guide

seems to make sense

what the ****

Offline

Pages: 1

Board footer

Jump to

We use Fail. Fail uses FluxBB

[ Generated in 0.012 seconds, 23 queries executed - Memory usage: 564.9 KiB (Peak: 578.45 KiB) ]