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

»  » 

#1 2015-01-09 22:22:16

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

Skullz is the very best


Jet fuel can't make dank memes.

Offline

#2 2015-01-09 22:37:49

Fradeshan
Filthy Casual
From: the darkest casual lounge
Registered: 2014-07-26
Posts: 2,199
Fails: 0

Re: Skullz is the very best

i wanna be the [DP] + M
and have my ip address logged


wait what why

Offline

#3 2015-01-09 22:43:02

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

Re: Skullz is the very best

[DP] is a relic from before we had the warnings mod. It stood for Double Posting, and the +M (skullz17) meant that he had an allowed alt named skullz17.


Jet fuel can't make dank memes.

Offline

#4 2015-01-10 07:12:57

skullz17
Guy
From: chepfials.ml.org.biz.tk
Registered: 2012-07-19
Posts: 1,179
Fails: 15

Re: Skullz is the very best

I missed it. well a pic is good enough.

What's the [DP]+M thing? I mean is it related to the pic


aTBdyqM.png?1

Offline

#5 2015-01-10 11:16:21

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

Re: Skullz is the very best

You didn't miss it, it was only there for a few minutes while I grabbed the shot. It could have caused trouble for you logging in.


Jet fuel can't make dank memes.

Offline

Board footer

Jump to

We use Fail. Fail uses FluxBB

[ Generated in 0.014 seconds, 23 queries executed - Memory usage: 561.72 KiB (Peak: 575.33 KiB) ]