dChan
Anonymous ID: de28ad July 12, 2022, 11:05 p.m. No.16725346   🗄️.is 🔗kun   >>5351 >>5488

Thousands Of Truck Drivers Plan On Striking & Shutdown

 

In California, starts July 13, 2022 at 7:00 am PDT

 

3 day shutdown/protest over AB5 (Assembly Bill 5)

 

Los Angeles and Oakland are participating.

 

2 minute announcement:

https://www.youtube.com/watch?v=DfIDYPjrWgA

Anonymous ID: de28ad July 12, 2022, 11:10 p.m. No.16725353   🗄️.is 🔗kun

ArchiveAnon

Current state of investigation:

 

I believe I have determined with 100% certainty that the issue with the Daylight Savings crossover timestamps is isolated entirely to the single thread in which they happen.

 

I was able to use the unix timestamps of the images posted in the threads on either side of this date, includeing ones posted by Q himself such as post #14, and confirmed that the hardcoded Unix timestamps embedded in the image urls return the times corresponding with their official timestamp.

 

Using this method I was able to narrow in on the thread in which posts numbers #92 - #96 were made during the crossover from EDT to EST.

 

Something must not have been calibrated right between this one single thread and whatever person or scraper program assigned the official timestamp entries for this series of posts, which managed to skew the timestamps forward by one hour for what appears to be a short series of only 4 posts.

 

The posts with the faulty timestamps, as far as I can tell at the moment, are #93, #94, #95, and #96.

 

Each of these posts has an official timestamp which is one hour ahead of the actual time it should be.

 

This is my preliminary finding and I still need to write up a proper report and walk through my reasoning, but it is the only conclusion I can come to currently which accounts for all of the evidence I can see.

 

The case appears to be solved.

 

https://t.me/s/ArchiveAnon