- Joined
- Jan 25, 2024
- Messages
- 2,427
- Reaction score
- 34,100
Thank you, Linda. I did listen to the whole trial while it was happening, so I did listen to prosecution as well as the defense. I am happy to explain my reasoning a little further. All IMO.No, we don’t know timestamp cannot be wrong.
When listening to testimony it’s important to listen to all of it. Not just the defense.
Search engines like Google record the exact time a search query is executed using server-side timestamps. When you perform a search, the request is sent to Google’s servers, which log the exact time of the query using their synchronized clocks. This ensures that the recorded time reflects when the search was processed, independent of the user’s device clock.
Furthermore, experts testifying on behalf of the prosecution stated that the 2:27 a.m. timestamp reflected when the Safari browser tab was initially opened, not when the search query was executed. They claim this was due to the WAL (write ahead log). I find this to be an intentional conflation, and in my opinion, this is not possible. The timestamp in question comes directly from Google’s servers, not from Safari’s WAL . It cannot be altered due to tabs being re-opened, new searches from the same tab, etc. It is an accurate reflection of when Jen McCabe made the ‘hos long’ search.
As always, all IMO unless substantiated by source.
Last edited: