|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools |
Rating:
|
Display Modes |
|
|
|
#1
|
|||||
|
|||||
|
Re: [FRC Blog] Einstein Report Released
Quote:
I believe there are far better ways to demonstrate these bugs. FIRST has held Beta Day in Manchester. If the FTA and some volunteering teams were on board, I'd be okay with someone demonstrating a novel flaw the night before SCRIW and forwarding the information to FIRST. And if you feel the urge to break something at Championship, why not practice matches with your own team? The phrasing of Jon's email makes me believe the individual involved is (well, was) a mentor on a team. As the guy in denim says, we get the best of what we celebrate. There is no room for celebrating interference with any competitive FRC match, whether it's Einstein or Q12 at some Box-On-Wheels Extravaganza of a regional. There is plenty of room to celebrate mentors that discover field issues and disclose them responsibly. |
|
#2
|
||||
|
||||
|
Re: [FRC Blog] Einstein Report Released
Quote:
|
|
#3
|
|||
|
|||
|
Re: [FRC Blog] Einstein Report Released
Quote:
Alan did a great job of answering the question, but I'll add that the FCA is not itself anything to be worried about. It could be due to a typo, a forgetful user, or an attempt at cracking the password. The access point with logging enabled may log the mac address of the FCA client. As mentioned in a previous post, the FW bug means that teams who used encryption for build season, opened their programming laptop at the event and unknowingly attempted to connect to their own robot with their build-season password resulting in an FCA. This was investigated to determine if it contributed directly to issues on Einstein. Greg McKaskle Greg McKaskle |
|
#4
|
|||||
|
|||||
|
Re: [FRC Blog] Einstein Report Released
Okay, it's that time again where Libby chimes in with a seemingly unpopular opinion.
I want to stress that I am not trying to be accusatory, and I'm also not speaking for any of my teams, for FIRST, or for my family. This is all me, and only me. Quote:
I personally hope for the team to come forward. If this individual were acting alone, and the team can honestly say they didn't know about it, then the team should be able to say "Yes, Jimmy (or Susie) McHacker was a part of our team, we didn't know at the time what was going on, but our team didn't condone the behavior and they are no longer on the team because of their action. We're really sorry." (Obviously, being banned from the team is no longer necessary since they're barred from FIRST, but that's not the point.) Yes, there will still be people in this community that will reflect the actions of the individual onto the team... but those people would be wrong, and we'd know that. Quote:
Quote:
Quote:
Quote:
-- Regardless of the individual I want to thank the wonderful people at FIRST HQ, the volunteers that helped with the testing process, and, of course, the Einstein teams. This is the biggest disaster FIRST has ever seen and you all handled it with class and professionalism. Thank you for being shining examples of what FIRST teams and participants should be, even during the bad times. I'll leave you with a Woodie quote... "Understanding that gracious professionalism works is not rocket science. It is, however, missing in too many activities. At FIRST it is alive and well. Please help us take care of it." Thank you, all, for helping us take care of it. |
|
#5
|
|||||
|
|||||
|
Re: [FRC Blog] Einstein Report Released
Wow, I just found this:
Quote:
|
|
#6
|
|||
|
|||
|
Re: [FRC Blog] Einstein Report Released
Too subtle?
|
|
#7
|
|||||
|
|||||
|
Re: [FRC Blog] Einstein Report Released
Yeah, I guess. My fault.
All: Disregard the above, maybe I'll try again later. |
|
#8
|
||||
|
||||
|
Re: [FRC Blog] Einstein Report Released
Quote:
|
|
#9
|
|||
|
|||
|
Re: [FRC Blog] Einstein Report Released
My own personal wish is that this situation will serve as a somber discussion point within each team. What would the correct response be if YOU found this or a similar issue? What if ... 's are a very valuable teaching tool for life, and the FIRST community is a safe harbor for learning so many of those life tools.
The fact that this statistically unlikely combination of wifi components left the door to the FIRST field partially unlocked doesn't make it that unique. A lost wallet, an unlocked or easily bypassed physical door, an online account with a weak password, all of these take place day-to-day and are worth considering and discussing along with the Einstein vulnerability. All systems have weaknesses, and for me it is cultural expectations more than the strengths of the locks that provide a sense of security in my day to day life. I am not intending to make excuses for the field issues. Locks and alarms are certainly a necessary part of the solution, but what really counts is how people behave when the lock is missing and there are no witnesses. Relatively speaking, I'm still new to FIRST, and I'm still amazingly proud of the impact it has on people. The level of trust and generosity displayed within the community is practically unparalleled. And yet, it will not maintain itself. It can be improved. I hope that the ultimate outcome of this unfortunate situation is that thousands of individuals consider their own actions in this and similar what if ... scenarios and use it as motivation for self-improvement. Greg McKaskle Last edited by Greg McKaskle : 14-07-2012 at 11:44. Reason: still new |
|
#10
|
||||
|
||||
|
Re: [FRC Blog] Einstein Report Released
Quote:
Such a move would financially utterly destroy their company and in point of fact cause massive financial damage to the manufacturers that support them. Besides they are already banned from selling the Nexus: http://www.businessweek.com/news/201...amsung-s-nexus |
|
#11
|
|||
|
|||
|
Re: [FRC Blog] Einstein Report Released
Do you have the source for this? Because to my understanding, Apple sued Samsung and told them to stop producing the Nexus.
Last edited by O'Sancheski : 14-07-2012 at 10:55. |
|
#12
|
|||||
|
|||||
|
Re: [FRC Blog] Einstein Report Released
I am constantly amazed at how sarcasm challenged many people are Nate.
![]() |
|
#13
|
|||
|
|||
|
Re: [FRC Blog] Einstein Report Released
It's a joke, guys. I think he was trying to make an analogy between incriminating individuals and incriminating a whole team. It's not a great analogy for a lot of reasons, though.
EDIT: Late |
|
#14
|
||||
|
||||
|
Re: [FRC Blog] Einstein Report Released
Quote:
I can in point of fact still buy the Nexus, the Galaxy Tab 10.1 (GameStop has them) and of course the Galaxy Tab2 10.1 (which I just returned the other day for specific technical reasons). The court did not order them to even empty the distribution of the product. Merely to stop offering to sell new stock until the matter is resolved. Adding: Sorry but that's sort of not a funny joke. You do realize that I have relatives that supply parts to Samsung and I know other FIRST members that if they read that would be wondering where their paycheck will come from. It's a tough economy out there, and this is a popular topic for people to read. Please think before you spoof your joke might not be funny if someone else panics. Misunderstandings like that can themselves shift the value of a stock. Last edited by techhelpbb : 14-07-2012 at 11:09. |
|
#15
|
|||
|
|||
|
Re: [FRC Blog] Einstein Report Released
Quote:
Anyway, I don't think the team nor the individual needs to come forward. The team could easily come out and say that they didn't know about it/weren't involved with it, but whose to say that's the truth? I could easily say right now, "I did it.", and if I phrased it as an eloquent apology, people would believe me.* Also, just a random idea here, whose to say the team knows about it? Maybe the interferer didn't tell his/her team why they were leaaving, and just treated it as a retirement or something. Just throwing out some possible scenarios here. *For the record, no, that was not a confession, wasn't a smartphone owner when I was at CMP, and I was the only one on my team there. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|