News for hackers. Stuff that matters.

A comment on Jan 6 committee subpoenas Meta, Google, Reddit etc. after 'inadequate responses'. Parent comment

Re:Jan 6 committee subpoenas Meta, Google, Reddit etc. after... by gjsman-1000 on Friday January 14, 2022 @11:18AM (#29936339)
We have a chain of command in our government for when people die. First the President, then the Vice President, then the Speaker of the House, then the Secretaries in a predefined order, and so forth. Plus, the Secret Service (which protects the president) includes considerations for, say, Nuclear Bombing of the capitol and who would take over leadership if such a disaster should happen.

If the rioters had succeeded in murdering every single person in the capital building, there would have been a protocol in place with the leader already determined. The only way this would have been successful is if the rioters killed every single elected official and secretary in the building, followed by having the support of the Army. They were absolutely nowhere near that.

[ Parent | on HN ]
Re:Jan 6 committee subpoenas Meta, Google, Reddit etc. after... by cnelsenmilt on Friday January 14, 2022 @11:45AM (#29936791)
The president (and president-elect) weren't anywhere near the building and their safety was not at issue.

There is no federal procedure or "chain of command" for replacing individual Representatives and Senators -- that goes back to the states they represent, with either elections or appointments.

[ Parent | on HN ]
[dead]
Re:Jan 6 committee subpoenas Meta, Google, Reddit etc. after... by ModernMech on Friday January 14, 2022 @11:33AM (#29936605)
The way I like to explain it is that Jan 6 was a Denial of Service attack which would have shut down a critical service COV (Certification_Of_Vote). The COV service was designed to bring a new process online while initiating the shut-down sequence of a lame-duck process. But a rogue script in the lame-duck attempted to shut down the COV service, which would have resulted in a privilege escalation and caused the lame-duck to continue running past its expiration date. Thankfully the DoS attack subsided in time and the COV service resumed its normal operation.
[ Parent | on HN ]