Anonymous ID: 3d77c7 July 28, 2018, 9:51 a.m. No.2324860   🗄️.is 🔗kun

>>2324551

i'd believe it.

there's an element of 'gotta respect his dogged determination to keep flying that flag' to it, i think.

 

and it was fun hunting it down.

Anonymous ID: 3d77c7 July 28, 2018, 10:23 a.m. No.2325167   🗄️.is 🔗kun   >>5218 >>5258

>>2325121

(point is the "nuke CoC" is a red herring. if they fired a NUKE from a sub or from land at AF1, we would know it in all sorts of other ways. it had to have been some other non-nuke missile. gut says tomahawk, but really want navyfags to weigh in)

Anonymous ID: 3d77c7 July 28, 2018, 10:32 a.m. No.2325267   🗄️.is 🔗kun

>>2325195

from what i've found (and posted) it appears that the launch auth can only be bypassed by a fleet flag officer (admiral, vice admiral, rear admiral, rear admiral lower-half) because they make the call once the strike has been 'authorized'.

 

if the auth came from DC, it would still be 'authorized' because their orders are defacto authorized.

 

(this is my basic understanding, not an expert)

Anonymous ID: 3d77c7 July 28, 2018, 10:35 a.m. No.2325296   🗄️.is 🔗kun   >>5335

>>2325207

>>2325195

 

ah, so thinking about this more - two scenarios are possible, because fleet flag officer doesn't make the "decision", they just pass it along.

 

either:

 

1) someone spoofed auth from DC, in which case we have no idea who could create the order

or

2) one of the fleet flag officers made the decision on their own.

 

if someone was removed, per Q, then they must have known instantly who generated the order, which still makes me think #2 is the scenario (but open for disagreement)