Let us never speak of this day again.

it couldn't be worse. /b/ really dropped the ball on this one.

fucking hilarious

Why were you in /b/? I dont think I can trust you anymore.

hehe furfags ruin the day again

i'm never going to /b/ again, for this has been the ultimate embarrassment,

I, for one,welcome our new furry get.

The ivory tower that is /b/ is now collapsing under its own weight, I fear we will be flooded

>>2293541
we're already getting flooded. I've already nearly given up on r9k

i rthink it was some sexyfur

I laughed my head off. Not that i care about furries but it's hilarious that this should happen to a culture that hates them so much.

I guess moot now has to make a /fur/ board.

Why do we share a server with them?

>>2293566
Because /r9k/ is really just middle-age /b/ (y'know, not when 4chan was new, but before all the Chanology shit).

>>2293566
Yeah, /r9k/ had to be down for like 20 minutes or something. I can't go without /r9k/ for longer than 2 minutes damnit.

My prediction was that Moot would give us his news update at 100M GET, so come on Moot. Don't let us down.

Look at the file names, it's shooped.

we'll never know if it's legit or not though
weep

>>2293565
furhating is a pseudo-meme and group behavior.
YIFF IN HELL DASU DASU U RAFF U RUSE RATE MY PENIS DERP EPIC WIN I GUESS THIS IS WHY THEY CALL THIS FORUM RANDOM XD etc.

after parties at:
http://lulz.net
http://img.7chan.org/lorf/
http://img.fapchan.org/fur/

obviously in /b/ itself. m00t is holding teh hammer

lrn2filename plox

>>2293583
those threads are not open, so you can't see their file names shooped or not failget is failed.

>>2293583

It's not. There were several different independent screenshots of the furry thing. I think it's just a bug or 99999999 is shooped.

GET IS A FAKE

LOOK AT THE FILE NAME NUMBERS

>>2293583
THEN WHO WAS 100MILLIONZ GET?

>>2293615good point

disregard >>2293614 i suck cocks

>>2293583
>>2293614
Nope. The system breaks down under extreme pressure (multiple posts per second especially). This is why, for example, if you were lurking /b/ while the GET rush happened you'd see posts out of numerical order in the list.

>>2293565
There was a /fur/, for about a week. Then everyone who posted on it was banned.

>>2293627
Protip: You're an idiot and/or a newfag.

I don't hate furries, but that one had me FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF'ing for about 10 minutes.

>>2293653
Wasn't it April 1st-2nd?

>>2293650
thinks he knows what he's talking about, but doesn't.

>>2293679
Yeah, >>2293650 (and OP, for reference) here, I don't really. Just going by what I observed.

What's true is that shit fucked up. It's not a shoop. Look at all the independent screencaps of it.

thing is, i was watching it tick over.
/b/oard was running slow at about 25 posts every couple of minutes and then suddenly the count jumped from 99999873 to 100000220sumfin.

the board name changed to 100M and then to what you can see now.

>>2293653

i really hope that thats true

>>2293653

THEN THIS IS KARMIC JUSTICE AT ITS MOST ACUTE

On the bright side, it wasn't the worst of the potential furry 100m GET posts we could've witnessed.

.
.
.
...I hope.

>>2293705
I don't know if 4chan did it, but SA did that a few years ago for april fools. It became known as the lollercaust.

>>2293777
4chan did it in '05.

it has obviously been a modget

This was not the first furry get.
Pokemon and catgirls count, denialfags.
100% human.

And the second evidence i submit to you.

it was an illegitime get, obviously.

the best thing about this is everyone on /b/ is whining about not knowing what the get was...and then denying it was the real get because the images have the same file name...if /b/ didn't post camwhoring, post-ending-in-blah-wins, CPing, DURR HURR shit every 5 seconds then maybe they would have actually seen the get for themselves...assholes

>>2293868
But then it wouldn't be /b/, now would it?

all of this is shooped. attached is what really happened

i just can't express how disappointed i am by this latest failure. fortunately we are all constrained to never speak of it again, so i don't have to.

10__0M

>>2293868
Wait, 100 000 000 GET and people actually missed it due to excessive flood and now are bitching about it?

Their stupidity never ceases to amaze me.