rabblerouser |
11-21-2018 09:35 AM |
Quote:
Originally Posted by RunKC
(Post 13908104)
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">My favorite part was the crew spotting the ball at the 12 for the <a href="https://twitter.com/Chiefs?ref_src=twsrc%5Etfw">@chiefs</a>’ final drive after the ball had been returned to the 15, plain as day. Who needs three yards when you’re trying to get into FG range late? <a href="https://t.co/N8b83ekRKL">https://t.co/N8b83ekRKL</a></p>— Mike Sando, ESPN.com (@SandoESPN) <a href="https://twitter.com/SandoESPN/status/1065259020821221376?ref_src=twsrc%5Etfw">November 21, 2018</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
I looked back on the DVR and this is 100% true. What in the ****?
|
The NFL doesn't respect its fans enough to count that high.
The guy in the earpiece told the ref to spot it there.
Amazing, how NY will buzz in and call for a review or even flat out overturn bad calls that go against their agenda, but somehow, in the most hyped regular season game EVER, with no other distractions and the entire football world watching...NY office lets ALL THIS SHIT go uncalled.
How would any reasonable, free-thinking adult NOT think this shit is rigged, is what I need to know.
|