If I were United Airlines, I would monitor the @UnitedAirlines (or whatever they use.) I would then report any threats (implied or direct) the the TSA.
No genius about it.
If you are flying and have a problem with your airline, tweet that you are getting screwed by @Delta, and see what happens. Last time it took about five minutes for a response.
So that process would attempt to guard against people who were actually attacking planes, but were stupid enough to tweet about it in flight and refer directly to the airline they were flying in their tweet.
I’ve never heard a case of a highjacker or attacker - a real one - being stupid enough to publicly communicate about their attack while they’re doing it.
If they actually wanted or needed to communicate to some co-conspirator on the ground, etc., all they need do us “use code names” - like they did in “Raising Arizona”.
Call the airline #doggypoo or something.
I #scooped the #doggypoo, over and out.
Something like that.
No, it clearly was a move by the Chris Roberts fellow to get attention, perhaps he wants a job working for them to fix the flaws he says he’s found, and he certainly got attention from them. I don’t know if they’ve hired him yet.
It does seem to this programmer / passenger like a crazy screwy thing to be able, as a passenger, to monitor the planes engine data in flight.
I don’t think I want to fly until this is resolved. I don’t want passengers having any access to anything in the planes systems.
If I worked for the airline, I would want to know that Chris Roberts or anyone else could not no way no how access any of the planes systems ever. That capability should reside only with the plane’s crew.
Throwing the dude off the plane obviously does nothing to correct the situation if there is a situation. If there is not a situation, the airline needs to prove Chris Roberts wrong publicly.
Perhaps the airline does not want to take the trouble to do that.