TL;DR
The year is 2026. We have 4K cameras in our doorbells, yet the mainstream media is currently looping a 24-second, 10-frames-per-second blur as the definitive evidence of an assassination attempt on the sitting President of the United States.
I reverse-engineered the Truth Social and Rumble API endpoints to bypass the web player and extract the original raw file uploaded to the President's account. The metadata proves that the video isn't just bad—it is fundamentally broken. When you combine the technical data with the physical layout of the room, you are left with a massive timeline paradox and a media apparatus that is blindly regurgitating a curated psyop.
The "Fake 480p" and the 435KB Paradox
If you watch this surveillance video on the news, it looks like a standard (albeit highly pixelated) security feed. It isn't. The media and video platforms are actively band-aiding the footage to make it look legitimate.
By querying the Truth Social static-asset API directly, I pulled the original master file (89dae6bf6a1c161d.mov) uploaded to the @realDonaldTrump account. Here is the raw metadata:
- Resolution: 176x144 pixels (QCIF).
- Framerate: 9.95 FPS.
- File Size: 435 KiB.
The 480p version circulating online is a fake upscale. Rumble's transcoder took a microscopic 176x144 file and artificially stretched it, bloating the bitrate with empty padding so modern video players wouldn't crash.
We need to stop asking how the video got this compressed, and start asking why this is the video they want us to see. This is an attack on the active Commander-in-Chief at a heavily fortified federal perimeter. In an era of instant, high-definition digital backups, why is the flagship piece of evidence a 435-Kilobyte, 10-FPS slideshow? A video this degraded strips away facial features, weapon identification, and spatial depth. It is the perfect medium if you want to show action without revealing any details.
The Geometry and Timeline Paradox
The degraded quality serves a purpose: it hides a massive physical contradiction in the timeline.
Look at the very first frame of the video (00:00). Before the runner even enters the screen, there is already a figure lying prone on the ground directly next to what appears to be an x-ray baggage scanner and folding table. A second later, the runner sprints past the checkpoint.
Now, look at the press photos of the suspect (Cole Allen) being apprehended. He is face-down, detained by tactical officers in what appears to be essentially the same area.
This creates a paradox that destroys the official narrative:
- The media & Trump claims the runner is the suspect. But if he is running away from the scanner, who was already on the ground next to it? Did the Secret Service tackle him off-camera and drag him all the way back?
- Who is already on the ground at 00:00?
By uploading a clip that starts after someone is already on the ground, the release strips away the context of the initial confrontation.
The Media's Complicity
The most alarming part of this event isn't just the 144p video; it's the fact that the entire mainstream news apparatus is running it on an endless loop without a single critical question.
News anchors are treating a 435KB, out-of-context cell phone recording of a playback monitor as the gospel truth of a presidential assassination attempt. They aren't asking why the timeline is sliced in half. They aren't asking why the quality is worse than a 2005 flip phone. They are just repeating the narrative that accompanies the blur.
Next Steps (Crowdsourcing)
We cannot rely on the official video feed. To break this apart, we need the unedited reality of the street outside.
- We need to crowdsource local D.C. FOIA requests for the Body-Worn Camera (BWC) footage of the first responding municipal officers.
- We also need to pull the DDOT traffic camera archives for the intersections at Connecticut Ave NW & T St NW to see how the alleged suspect actually approached the building.
They expect you to watch a 10-FPS blur and trust the story they attached to it. Trust the metadata instead.