Hacker News new | ask | show | jobs
by bnt 1095 days ago
Would be easier if they had shared Slack channels
3 comments

What is communication like between different branches of the US military nowadays?

I remember reading a series of newspapers articles about the Somalia battle that was later the subject of the "Black Hawk Down" movie. I haven't seen the movie so don't know if it covered the communication issue I'm about to mention.

The army had a convoy on the ground trying to reach the crashed Black Hawk helicopter. The navy had a surveillance plane watching. The plane would see that the convoy was heading toward and ambush but they could not talk directly to the convoy (I don't remember if it was because they didn't have radios with the frequency the convoy was on or if there was a rule against it) so had to relay the warning and recommended alternate routes back to their own base.

There that would go up through the chain of command until reaching someone who was able to talk to a counterpart in the army, then down the chain of command in the army and finally to the convoy. By then the alternate routes the plane had found were no longer applicable, and the convoy might have even already reached the ambush.

When they got past that it would just happen again farther along with another ambush.

Saw the movie, but don’t remember that being part of the plot.
Best I can do is a flat file message transfer that runs weekly (with 18% success rate) between branch mainframes.
So, Teams?
As opposed to JSON push-notification payloads over webhooks run by a SASS GovCallbacks.io and costing 15$ a month for?
Implemented by IBM using Oracle, for some reason.
Or maybe a Discord server, where they could share all their Top Secret...

OOPS! nevermind.