Hawaii "button pusher" refusing to cooperate with FCC, internal investigators
staradvertiser.com
staradvertiser.com
Useful background info: “Don’t talk to the police” video from a law school class https://youtu.be/d-7o9xYp7eE
That's not at all true. Now, it may be true that it is not a crime not to speak to them, it almost certainly is a legal obligation attached to his employment and he quite likely will be fired for cause if he continues to stonewall.
We all know stories about what appeared to or was claimed to have happened that reached the media through official and unofficial channels before any internal investigation.
http://www.civilbeat.org/2018/01/hawaii-distributed-phony-im...
(Quite a load of BS, that statement.)
http://www.businessinsider.com/hawaii-emergency-agency-passw...
I suspect that the picture of the UI problem that has become public is likely accurate as far as it goes, but is also far from a complete picture.
I was just thinking that!
I can just imagine (in my own head, of course) that this guy has been banging pots and pans talking to executives and those above him to set aside the time and/or budget to fix the terribly archaic and sensitive system. Now he's sitting there looking guilty as possible and his only way out is to throw everyone who ignored him under the bus.
Why do I assume that things are this way? I feel like I've dealt with 20-30 different situations like this in my ~12 years programming and of course they were WAY smaller in comparison but there is no "clean way out". Feelings are going to get hurt and the work place's fabric could be torn to shreds. Nobody wants to be responsible for that.
If an air traffic controller was involved in a plane crash in a non-culpable manner, I'm sure people would feel very strongly that he should cooperate with investigators. Why is this situation different?
> Pursuant to section 701(e) of the Federal Aviation Act of 1958 (FA Act), and section 304(c) of the Independent Safety Board Act of 1974 ( 49 U.S.C. 1154(b)) (Safety Act), no part of a Board accident report may be admitted as evidence or used in any suit or action for damages growing out of any matter mentioned in such reports.
https://www.law.cornell.edu/cfr/text/49/835.2
You may also want to read more about how we got here, too:
Crucially, the National Transportation Safety Board's purpose is to make safety recommendations, not to enforce law.
I seriously want to give a hug to the person who mis-clicked. If you have seen that UX design, you know as well as anyone else, that indeed, most would have mis-clicked over time.
The people investigating this are making a huge mistake.
I don't blame the guy for not talking any more - he's (rightly) scared of being crucified for misclicking.
The smart move is to stfu, call your union representative, and don’t talk to the police until your lawyer makes the appropriate arrangements.
Edit: And STFU is smart advice in any situation where there is even a remote chance you will be charged with something. You can always make a careful statement later on advice of counsel. Nothing is lost by remaining quiet at first.
See
http://www.civilbeat.org/2018/01/hawaii-distributed-phony-im...
http://www.civilbeat.org/2018/01/hawaii-distributed-phony-im...
It's a common enough UI issue to be immediately clear to a professional how it happened though.
The level of incompetence is astounding!
> “We asked (Hawaii Emergency Management Agency) for a screenshot and that’s what they gave us,” Ige [Hawaii Governor] spokeswoman Jodi Leong told Civil Beat on Tuesday. “At no time did anybody tell me it wasn’t a screenshot.”
So the governor asked for a screenshot and they sent him a "mockup" instead of the actual interface?
I can only assume the actual interface was somehow even worse than the fake.
However, I'd still stand with Peter here [1] and think they just could not get the "screenshot tool" installed to the machine.
Amazing.
There are many things say. That's probably why they want to talk to him. Was it a random mistake? Did anything else contribute? Was he on Hacker News writing a comment at the time? Was he tired, sick, under the influence? There were other people including a supervisor, did the supervisor approve, did they double check later? Did they distract him somehow?
They might conclude it was the stupid user interface but they'll still do the legwork of investigating and getting all the details. One thing they definitely don't want to do is answer the question of "Did you try to talk to the individual?" or "Nah, we saw online how everyone was jumping on redesigning the UI and assumed it had to be that so never talked to him".
> You can always make a careful statement later on advice of counsel. Nothing is lost by remaining quiet at first.
That's what he did it seems: released a written statement then STFU. Hopefully he got a lawyer cause it seems he'll need it.
> Nothing is lost by remaining quiet at first.
True. Ideally it is the best strategy. But here it is drawing more attention to the case. It's in the news again. And he is also getting death threats.
sure the UI as shown is bad, but we got a static screenshot so no, it is not blatantly obvious to me how likely an operator error actually is.
Was it there a confirmation dialog afterward? How often was the UI in this form operated? For how long was it deployed? Was that interface something one user would see during normal operations or only accessible after a warning dialog?
> STFU
that's right tho. anything one say will be used against oneself and all that. there will be layers of cover up as with anything involving government officials and private contractors, he need to tutelate himself to even have a shot to reach a fair charge.
Maybe, maybe not. I mean if there is a remote chance you will be charged with “something”, possibly minor, whether or not you cooperate, and a practical certainty that you will lose your public employment and associated benefits if you don't cooperate (and, likely, your employability anywhere related to your chosen field), you probably want to do a more detailed consideration of the likelihood you will be charged, the likely consequences if you are, and the marginal risk of talking.
This guy is a button pusher at some random state government agency. Probably not the extroverted types who handle global media attention and ridicule well, let alone the guilt and shame of scaring the hell out of everyone in your state.
Especially given the phrasing of this:
> “He’s choosing not to have further engagement with other employees at the Emergency Management Agency who have attempted to reach out to him.”
From public accounts, it doesn't sound like he messed up badly, he just made a minor mistake than anyone could make.
But they'll try their hardest to pin this on a scapegoat and he is the obvious choice. I'm not sure I'd cooperate either, particularly as lying to the federal government (any agency) is a crime within itself (18 U.S.C. § 1001) and even omissions or a poor memory can be argued that way (even if they're ultimately found not guilty the public would have lost interest by then).
I'd get a lawyer, say very little, and maybe give a written statement of facts to the investigators, nothing more.
That excuse seems to work for our elected officials...
The obvious choice, if there was to be a scapegoat (which I won't prejudge the officials involved to be seeking), until now was whoever designed/build the system in question (particularly it's UI), who had pretty much already been convicted in absentia in the court of public opinion (possibly based on fabrication, as it turns out.)
Now he’s the obvious choice, but that's almost entirely a result of his own actions.
His own actions being following sound legal advice..?
Choosing the wrong menu item should be expected and there should be safeguards to prevent an errant alert. If I click the "Close" instead of "Save" menu item in my editor, it asks me to confirm that I really want to close without saving. A civil warning system should have at least the same safeguards.
The other is how to deal with being arrested, or targeted in an investigation. "Refusing to cooperate" is always the smart move. Because cooperating will always make it worse, notwithstanding claims to the contrary. And it's sad that this person is being criticized for being smart.
IIRC it took them over half an hour to issue a correction.
Imagine if airline employees didn’t cooperate in crash investigations. Or restaurant employees in outbreak investigations.
You shouldn’t be brash and speak without counsel, but stonewalling an official investigation will not end well for the stonewaller.
Also, "cooperating" implies some shared goal. Such as discovering the facts of the matter. But that's very likely not the case here. These investigators arguably need someone to blame, and the likely candidate is pretty clear. The "button pusher" needs to focus attention on underlying problems, and that's a huge burden for a drone. Others with expertise need to do that.
When I was a teenager I realized you could set of the emergency alert system with a dtmf 4 digit code on some 144mhz with a ham radio.
I never did it, but I pretty much expect that to be still possible.
The reason I say this is because yes, it is possible someone got the wrong button, but shit software like this probably has vnc with no auth/useless auth so someone can activate remotely
I'm assuming this was from the past ("when i was a teenager") when the messages were much more generic and fixed than they are today.
It definitely is from my teenage years but whenever I visit folks I drive by that tower a block away. You can tell nothing has been upgraded
Smart system, really. Very simple to install/maintain and very simple to have a robust transmitter infrastructure around.
If you just substitute your 4-digit code for a longer, say, 64, digit one with some time-based component, and perhaps shift the required frequency too based on time, you actually end up with a very robust very simple system.
As far as I'm aware this is still the case - but some sites are now encrypted radio. From what I've heard though, that encryption may not be the best implemented in all areas.
It was pretty recently someone set off the civil warning sirens in I believe a city in Texas via this method as well.
I'd like to say this was a one off experience in my "exploring civil infrastructure" days - but it's really just barely scraping the surface. The state of these systems makes you realize how much civilization is held together with tin cans and duct tape, and how much marketing fluff there truly is out there inspiring false confidence.
The government would be stupid not to do this on purpose.
While it's worryingly similar to crying wolf, I would hope that this does lead to more of the general public (even outside of Hawaii) actually thinking about how they'd handle and react to an imminent threat.
Mandatory witch hunt is failing apparently due to good union/legal firewall.
Wish we could see that more often.
Too many good people fallen to that.
> So, as it turns out, the culprit who induced panic among over a million Hawai'i citizens isn't nearly as contrite about his mistake as his superiors would have us believe. In spite of legions of supporters who have urged us to drop demands for his dismissal, he now has the audacity to be uncooperative in the investigation into the serious event that he alone triggered? Then TERMINATE him....
Bloody obvious why cooperation is being withheld.
This was a poorly designed software interface.
Operators should not be blamed for government-mandated, piss poor alert systems. The government is responsible for this fiasco, not the button pusher.
They have nothing to gain and a lot to lose by complying with an investigation.
If they had clicked the wrong button in a moment of distraction then that might not be the end of the world, that could be fessed up to. However, what if they were pissed off with their micro-manager and thought that their 'accidental click' would result in the manager's scalp? A whole lot of things would then need to be looked into and it might not be a simple accident at all, but the visible result of a lot of festering office politics.
An officer asks you, "Do you know why I pulled you over today?"
- Yes = admission of guilt. You're screwed.
- No = indication of disregard for law, recklessness, and no situational awareness. You're even more screwed.
- Good afternoon officer, I'd rather not answer any questions. Would you like to see my license and registration? = Bingo.
>The employee has not been disciplined but faces the possibility of punishment, which could include termination, Anthony said.
Is this normal in the US. Govt. that you can not go to work for 2 weeks and there has been zero disciplinary action?
HI-EMA is not part of the US Govt.
> that you can not go to work for 2 weeks and there has been zero disciplinary action?
It's true most places, not just in the US and not just in the public sector. They did not indicate whether he was away with or without leave, and if he was on leave for medical (including psychiatric) reasons, there are privacy considerations which might prevent revealing that.
OTOH, if he is away without leave consequences are near certain, but the disciplinary process in the public sector may be slow (and it may deliberately be deferred in this case to maintain leverage for his cooperation in the investigation, which probably had more critical importance—especially if it's not a hunt for a scapegoat—than an attendance problem.)
(Bonus points if the video is not of the actual live interface.)