Loading video...
Video Failed to Load
🚨MUST READ UPDATE: Baltimore Bridge Collapse The Cargo Ships BLACK BOX Reveals the VDR Sensor Data “Ceased” Recording for 2 Minutes Prior to Impact 🔴 NTSB investigator Marcel Muise held a press conference to reveal the data on the DALI’s black box, also known as the Voyage Data Recorder... show more
6,416,305 views • 2 years ago •via X (Twitter)
8 Comments
Those pesky "coincidences" are stacking up
We better not question anything or we’ll be evil conspiracy theorists. This story will be buried right next to Vegas and the Maui land grab going on.
And still, hardly and chatter about the thermite charges that cut the bridge into sections, making this a controlled demolition. The boat accident is just for cover.
Why on earth would they just drop the port anchor? That would be why the ship turned sharply left and ran into the bridge. That seems deliberate to me. They were going to clear it, then should have dropped both port and starboard anchors at once to slow down the vessel to a stop?
Big surprise, you look at the original video, you see it turn toward the support structure, and you see thick diesel smoke pouring out the stack, (like they gunned it).
doesn't that huge plume of smoke mean they hit the gas hard af?
The ship was hacked and you can watch as the crew tries to reset the system twice by shutting off the main power, but to no avail. You can even watch the black diesel smoke as the engines accelerate towards the bridge pylon. It was planned and everyone in the government is lying
10 billion for bridge 10 billion for Ukraine.hopefully this explains it.
![Yesterday, Ian Whiffin confirmed what Richard Green/the #KarenRead defense said in Trial 1, thus confirming that John O’Keefe arrived at 34 Fairview 3 minutes & 1 second before the Commonwealth’s GPS/location data points show: “[The monotonic clock] is not a clock that can be trusted to see when events occur.” Only the display time is accurate when determining when something actually happened. “All activity is related to that (the display) clock.” “You have to take the values that the monotonic clock provides and add or subtract different values, which are essentially offsets, to get the correct time.” That’s a major problem for the Commonwealth — because Whiffin’s entire Waze location analysis is built on the MONOTONIC TIMESTAMPS! And somehow, neither Whiffin nor Hank Brennan seems to grasp what just happened: They accidentally proved the defense’s theory! Specifically, because the Waze app runs on monotonic time programming and not the display time programming, the timestamps associated with the cached locations from Waze on John’s iPhone are 3 minutes and 1 second fast/ahead, or have a 181 second offset (see attached evidence exhibit from trial 1 with the specific conversions). This means that John O’Keefe arrived at 34 Fairview at approximately 12:21:37am, give or take, and not at 12:24:38am as the Commonwealth asserts, as Waze is based off of the monotonic timestamps, not the display clock timestamps. Consequently, this means John arrives at 34 Fairview BEFORE his Apple Health data recorded him taking flights of stairs, which didn’t first occur until 12:22:14am, therefore meaning that approximately 40 seconds after arriving at the house, John O’Keefe first began climbing some stairs. It suddenly becomes a lot harder for the Commonwealth to discredit the reliability of Apple Health data confirming John went inside the house when his location data also put him there. Why would the Commonwealth rely on the wrong timestamps when conducting their 15+ months after the fact GPS/location data analysis? Because it was right after the defense had first made public John O’Keefe’s Apple Health data showing flights of stairs climbed upon John’s arrival at 34 Fairview—thus establishing that he did in fact go inside the house. They needed to keep John out of the house to have any case, so they opted for discrediting the Apple Health data they so regularly rely upon in their criminal prosecutions, while deliberately only looking at John’s phone location data sourced from the one app that uses monotonic time programming without converting those timestamps to the display time (or subtracting the 3 mins. 1 second offset). By exploiting the incorrect monotonic timestamps of the cached Waze location data, the Commonwealth was able to claim that John’s phone location data showed he’d not yet arrived at 34 Fairview by the time his Apple Health data showed him climbing flights of stairs inside the house. To convert any of John O’Keefe’s Waze data that Whiffin presented into real time, you need to subtract 3 full minutes from each monotonic timestamp. So when Whiffin bizarrely testified that John was climbing stairs while driving down Oakdale at 12:22 AM? Yeah — that actually happened at 12:19 AM. And when he claimed Karen pulled up to 34 Fairview at 12:24 AM? That was really at 12:21 AM. Both times perfectly aligned with the Defense’s timeline. Not the Commonwealth’s. And Hank Brennan? Well, he’s got his expert, Ian Whiffin, casually confirming that John O’Keefe was walking into 34 Fairview at 12:21 AM, and climbing stairs at 12:22 AM. At this point, you really have to ask: Are the Commonwealth’s witnesses planning to leave anything for the Defense to rebut? Or are they just going to blow up their own case — one by one? Because this? This is getting insane. #IanWhiffin #Cellebrite #NorfolkCounty #KarenReadTrial #KarenReadTrial2 #FreeKarenRead #JusticeForJohnOKeefe](https://image.24vids.com/tw-1917205496362328131/amplify_video_thumb/1917205398630670336/img/GNAAuPE59r5bEqJV.jpg)
