GAME WEEK ADDENDUM

I regrettably direct your attention to this post on the blog, “Temple Football Forever.” It was brought to my attention earlier this week, and at the time I didn’t give it much thought. Dumb stuff posted on the internet is hardly a new phenomenon, after all, and I’m not one for blog-on-blog e-beef. That changed, though, when the guy edited his original post to include a link to a comment made here after last year’s game. If he’s going to involve my site as part of his spectacle of stupid, then it warrants a response. Contrary to the loquacious nature of most of my posts here, I’ll keep it short. (Crap, I’m failing already.)

If you’re anything like me, then your general appearance after reading such profound literature looked something like this:

I mean, it’s understandable that a Temple fan might be a tad bitter about his team’s collapse in last year’s game. But this? This is a manifesto for the maladjusted. I’m not sure what the best part is. We have:

  1. The complete lack of understanding of the nature of college football scheduling, leading to tin foil hat-worthy conspiracy theories. Buyout terms are included as part of a contract, not paid when terms are violated, and are exercised fairly often. That’s no help in the quest for victimhood, though.
  2. The idea that Navy, who needed the scheduling change in part to be able to play in front of 100,000 Ohio State fans, sought to change the schedule so as to avoid playing in front of 17,000 Temple fans.
  3. The e-hit he puts out on some random Navy fan he apparently thinks is a fixture in Annapolis.

The Middies have a fan who blows whistles when Navy ballcarriers are seemingly stopped, yet the fan never gets kicked out of the stadium and game officials feign deafness around him.

Seriously? This is a regular occurrence? This fan sits at Navy games, looks for Navy players in distress, and blows whistles when they’re in trouble? Really? I mean, that would be awesome if it was true. That’s sort of like a superhero. That would mean that there’s a Navy fan that actually cares about the outcome of the game more than the length of TV timeouts. I hope one day to meet this person.

The pièce de résistance of the post is the author’s description of the effect this mythical superfan had on the game. Here is the play in question… Be sure to watch the whole thing, because you need to hear the ref explain the penalty flag:

OK, so let’s break down what our Lone Gunman said, and compare it to reality:

He’s the guy who blew a whistle three times while Temple defenders stopped a ballcarrier on fourth and goal, only to see the guy get off the ground and run into the end zone with the officials signaling touchdown and Temple coaches yelling, “what the fu*k?”

Let’s say there was a whistle from someone in the stands. I’m not sure if there was or not, let alone one blown three times, but we’ll go ahead and assume that there was. So who is it that got up off the ground, exactly? Eric Kettani is the fullback that received the pitch and ran it into the end zone. He was never on the ground, and was hardly even touched. Ricky Dobbs is the quarterback, but he isn’t who scored. He didn’t touch the ground either, at least not while he had the ball (more on that in a sec). This was the only 4th & goal of the game, so our esteemed blogger isn’t referring to another play. If you think he might’ve simply mixed up the down & distance, he didn’t. Here’s every play Navy ran in regulation, so you can see for yourself if you’re so inclined.

Then, we have this gem:

Temple players stopped tackling the Navy guy for fear of being called for a penalty, only to see the Navy guy score after the whistle.

I don’t get it. Did the guy get up off the ground? Or was he never down in the first place, since the Temple players stopped tackling him? Clearly the first description of this play was just made up in the dude’s head, so we’ll press on with the second. According to this guy, Temple players stopped tackling Ricky Dobbs after hearing a whistle, “for fear of being called for a penalty.” In reality, not only did they not stop, but they actually were called for a penalty! And for throwing Ricky to the ground!

Watch the video again. Can you point to anyone that looks like he heard a whistle to you? Anyone who stopped playing? Hell, Navy players have good hearing, what with all the DOD medical requirements and such. Do any Navy players looked like they stopped playing, or is it a special whistle only Temple players can hear?

To recap: nobody was ever on the ground, and not only did Temple defenders not lay off the quarterback, but they were flagged for throwing him down. Reality bites. Don’t drink and blog, kids.

Advertisements

17 Responses

  1. Neutral guy here, as I found this blog via being a Georgia Tech fan.

    Best guess I have is that he’s trying to make an argument that Dobbs should have been stopped due to forward progress before the pitch; but that’s certainly not what he said, and it’s certainly not borne out by the play on the field by any of the defenders.

  2. That’s clearly not the argument he made, and you would need the fastest forward-progress trigger ever to blow that play dead. Not that it matters, because nobody stopped playing.

  3. best part of the TFF blog…he screens all comments

  4. There was a whistle. It was in the Temple section. It did not appear to affect the play on the field. It did affect the roller coaster of emotion in section 102, as several of us up there were fooled.

    This is the same guy that tried to say the mids were on the field during overtime last year. He was proved wrong by photographic evidence on that one too.

  5. You know better Mike. He’s an “award-winning journalist” after all. Why the heck don’t you just give up while you still can?

  6. lol

    I’m gonna stay on point with this one.

  7. Do you really listen to the bloggers that much? I never do.

  8. I also read most of the opposing teams blogs prior to the games and was baffled by that post. Having gone to every home game and last year’s bowl and Army game I have yet to see this famed whistle blowing mystery man in the endzone.

  9. And Mike, I volunteer for the job of whistle blowing mystery man, although I might need a bodygaurd or two to defend me from the TFF readers.

  10. After reading this blog I was like http://i43.tinypic.com/r9n6f9.jpg

  11. anon, i know you really think you’re good at being a smartass, but the answer to your question is contained in the first paragraph. please stop sucking.

  12. Just wanted to let you know that I (a Pitt fan) posted over at Temple Football Forever about how ridiculous this argument is. Let me get this straight – his theory is that Navy was terrified to play Temple in Philly so they scheduled the cupcake that is OSU in Columbus? Talk about illusions of grandeur.

    By the way, the reason I was here was to see when the Pitt-Navy game was next year…. I’m disappointed these teams don’t play again until 2013. My family went to Annapolis for last years game and loved it – even more so than our Notre Dame trip later that year. As a season ticket holder, I truly enjoyed watching unique offense in person every other year. Anyone know what happened?

  13. It’s just the way the contract was originally set up.

  14. forward progress was stopped. if there wasn’t a whistle, there should have been.

  15. maybe the concorde district player of the year could’ve made the tackle.

  16. The Concorde District player of the year is going to be the MAC and maybe the Big East player of year in the same career. When it happens, remember you read it here first.

  17. I’ll be sure to go some Temple blog to pose as a Temple fan and pretend to care.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: