Quote:
Originally Posted by Libby K
You're taking an incredible moral high road, and saying that this person feels sorry. Good for you for believing in people, but what if they don't?! Unfortunately I've seen plenty of attitudes that say "I'm GLAD Einstein screwed up, because FIRST sucks and they had it coming". Paraphrased from many emails/FB comments/tweets/what have you, but that's the sentiment.
|
And what if they don't? What's the proper course of action if they have no remorse?
Should we continue punishing them until they break down and say their wrong? They've already been blacklisted, now we should publicly out them? What if that doesn't work? Should we continue to "turn the screws" until we see them suffer?
Quote:
Originally Posted by 1075guy
As I recall (I've only been to CMP once), the number of people allowed fieldside at Einstein would be restricted to the drive teams of those teams participating on Einstein, plus some volunteers.
That leaves a VERY small number indeed.
|
While I haven't been to St. Louis, that's simply wasn't true in Atlanta. I was field side on Einstein myself in 2009, despite not being a volunteer or participant on an Einstein alliance. There are numerous people who find avenues to be field side at Championship.
Quote:
Originally Posted by 1075guy
|
According to
this post, 1717's issues were caused by a bad cable on the robot.
Quote:
Originally Posted by 1075guy
Why are you focussing on 25? As you mentioned, 25 had version B at Championship (and so did 16). They were protected (whether they realized it or not) from the FCA vulnerability because of it.
|
Because he's on team 11 from Mt. Olive, New Jersey located about an hour from the home of Team 25. He's had personal interactions with team 25 on the issue at hand and knew of their usage of that firmware.