Fascinating
Loved him in that show……has a new episode of Monk coming out on a streaming service, can’t remember which one, Peacock maybe???
@Herschel posted:The judgement call was that MVS ran out of bounds under his own volition and Ballantine was unable to stop him.
The other way would have been Ballantine knocked him out of bounds after esstablishing control and ending the play.
This. Is. Exactly. What. Occurred.
Keep trying, guy.
@titmfatied posted:Don't care for Skip, but good discussion by Irv and Sherman here.
Even Skip's mom doesn't care for Skip.
I was shocked that those three actually sounded reasonable on this.
Like dealing with The Fonz, or Trump.
@H5 posted:Keep trying, guy.
I think PackerRick has taken over Herschel's account.
@Herschel posted:No. A different example we've seen before is when a first down would be involved. If the receiver catches the ball past the sticks and runs out of bounds behind the sticks, the clock stops and there is no first down.
It's about control.
We know in that sitauation MVS would try to get out of bounds.
The judgement call was that MVS ran out of bounds under his own volition and Ballantine was unable to stop him.
The other way would have been Ballantine knocked him out of bounds after esstablishing control and ending the play.
When MVS crossed the boundary, he was moving backwards because of Ballantine's contact. Forward progress had been stopped because of Ballantine, and MVS was taken OB-backwards-because of Ballantine. It sounds like your argument is based on intent. But the rule is designed in part to eliminate the element of intent. Forward progress stopped=clock runs. Backwards out of bounds=clock runs.
The whole world knew that MVS needs to get out of bounds. But once he's engaged by Ballantine-and stopped and heading backwards- it's no longer MVS own volition. He was driven backward and the fact that he happened to make it to the sideline is overridden by the defender physically moving the player in the negative direction.
IT WASN'T A FAIR CATCH
LOVE IS UNDERTHROWING PEOPLE
@PackerHawk posted:I think PackerRick has taken over Herschel's account.
Did someone say PackerRickSmalley
Attachments
@artis posted:When MVS crossed the boundary, he was moving backwards because of Ballantine's contact. Forward progress had been stopped because of Ballantine, and MVS was taken OB-backwards-because of Ballantine. It sounds like your argument is based on intent. But the rule is designed in part to eliminate the element of intent. Forward progress stopped=clock runs. Backwards out of bounds=clock runs.
The whole world knew that MVS needs to get out of bounds. But once he's engaged by Ballantine-and stopped and heading backwards- it's no longer MVS own volition. He was driven backward and the fact that he happened to make it to the sideline is overridden by the defender physically moving the player in the negative direction.
It isn't my argument, it's a statement about how the refs saw/called it. Until we're employed as referees by the NFL, our opinions don't carry any weight, and if we were our adjudication would likely be far more biased. Simply put: That's how they saw it, that's how they called it, it's not reviewable, and it didn't affect the outcome. Complaining about it endlessly changes none of that.
In other words: I simply find it more productive to understand how/why something like this happens rather than digging my heels in about how "we were wronged".
Refs are human and every team's fans see calls they don't like. It's a football universal constant.
But as with backward passes by Steeler QBs, the refs can get it wrong even when watching the replay.
Sure, and that one is just weird to me, but since they were the refs their judgement still stands. I can think it was wrong, but all that and $5 gets me a cup of coffee.
@Herschel posted:It isn't my argument, it's a statement about how the refs saw/called it.
Are there some words posted out there on the Internet from the league or the officials that back this up? Everything I've seen points to they fucked this call up.
@PackerHawk posted:Are there some words posted out there on the Internet from the league or the officials that back this up? Everything I've seen points to they fucked this call up.
It's what they called and the way they resolved it. That's not opinion, it just is. It doesn't matter if you, I or anyone else thinks they fucked up, and complaining about it isn't going to change that. I don't have to agree with it to see what happened.
How would he get his member rank up that way?
We will never forget you PackerRay!!
I can think of one.
Obviously not #35.
A few numbers lower.
I miss #1!
@Herschel posted:It's what they called and the way they resolved it. That's not opinion, it just is. It doesn't matter if you, I or anyone else thinks they fucked up, and complaining about it isn't going to change that. I don't have to agree with it to see what happened.
Brevity, bro. Instead of writing essays in your previous posts you could have simply said something like,
”Fuck yo opinion. Refs get the final call, bitch”.
Short, sweet and to the point, with some Anglo Saxony thrown in to emphasize that point. No one would have argued with you.
This is….. embarrassing. What a take https://t.co/4uW6F3QZPE
— hales (@bailsofhayyyyy) December 5, 2023
This fully explains the Owens Mahomes play and the MVS out of bounds play.
Kyle Kirms is obviously a little bitch.
Interesting image. Not that there is anything wrong with it.
May not be text book, but I'm guessing the textbook didn't have a 250# guy about to smack you.
Does the fact that Owens was OOB’s have any thing to d with the call ?
Actually, I think it has everything to do with the competence level of NFL referees.
@Blair Kiel posted:Actually, I think it has everything to do with the competence level of NFL referees.
Saw your avatar girl's commercial tonight. She's got the moves like Jagger!