Sabitlenmiş Tweet
Sarah Isberg
2.3K posts
Sarah Isberg
@Sarah_Isberg
Research Scientist tech geek and MOM 😁
Katılım Eylül 2013
352 Takip Edilen251 Takipçiler
@WhiteHouse Why do we need a fucking app when we have X? Lame! When EBS?!
English
🇺🇸 🚀 LAUNCHED: THE WHITE HOUSE APP
Live streams. Real-time updates. Straight from the source, no filter.
The conversation everyone’s watching is now at your fingertips.
Download here ⬇️
📲 App Store: apps.apple.com/us/app/the-whi…
📲 Google Play Store: play.google.com/store/apps/det…
English
We do a little Analysis. @WhiteHouse
155 frames of near-black static. Enhanced 80x, every frame contains the WH building logo + "PRESIDENT DONALD J. TRUMP" buried in noise at ~2% brightness.
The audio is 2x the size of the first deleted video's. Continuous hidden track under static. Dominant tones at 281Hz and 472Hz. Forward then reversed+denoised at the end — listen with headphones.
Same GPAC 2.2.1 encoder, same anti-seek H.264, created 24hrs after the first. Engineered, not accidental.
The White House@WhiteHouse
🤫
English
@lalamocha4 It's probably the stupid phone like the gold on her shoes 🙄. x.com/i/status/20373…
English
English
I pulled apart the @WhiteHouse video frame by frame. 214 frames, ~60fps, 3.6 seconds. Here's what's actually in it.
The video was built with GPAC 2.2.1 (open source multimedia framework) before Twitter re-encoded it. Not a casual screen recording. The H.264 encoding has keyint=infinite and scenecut=0, meaning someone deliberately disabled keyframe insertion at scene transitions so you can't easily seek to the flag frames. That's intentional.
Frames 1-163: Grayscale static. All three RGB channels are identical (pure monochrome noise). No LSB steganography detected in the frames Twitter's encoder left us, but re-encoding would destroy that anyway.
Frames 164-165: The flag. When you brighten it 8x, it's a flag on a pole with VERTICAL red and white stripes and a blue star field. That's the Allied States of America flag from Jericho, a show about a shadow government nuking American cities and the country splitting apart. Two frames. Roughly 33ms of screen time. You'd never catch it at normal playback.
Frames 166-171: Remnants of a phone UI. A notification bar strip at row 388 and a status bar at the top of frame. This thing was screen-captured from a phone.
Frames 172-178: Horizontal banding pattern. Bright bands at irregular intervals across the frame. Not random noise. Looks like interlaced scan data from whatever source video was glitched up for the effect.
Audio: iPhone notification chime starting at 2.26 seconds. Clean multi-harmonic tone. Spectrogram shows harmonics at ~1kHz, 2.5kHz, 5kHz, 7.5kHz, 10kHz, 12.5kHz. No hidden spectrogram images (Cicada 3301 style). No ultrasonic content.
The Grok explanation that this is just a promo for the "Text USA to 45470" alert system doesn't explain why someone used GPAC to build a video with anti-seek encoding parameters and embedded a fictional secessionist flag from a nuclear apocalypse TV show in it. During an active military conflict.
Whether this is an ARG, a psyop, or the most unhinged social media strategy in White House history, the Jericho flag was not an accident. Someone put it there on purpose.
The White House@WhiteHouse
📱🔉
English
@Kaelan47 Oh hell no, is this about a stupid phone? Or the dumb alien site!? Sheesh, lol Oh hell no, lol x.com/i/status/20373…
English
@WhiteHouse Is this about the stupid alien site? With all the real shit going down right now... 🙄
English
@WhiteHouse Squint your eyes, someone looking down at their phone or someone getting arrested and in cuffs.
English
@encrypted_past @WhiteHouse How did you determine 589 or is it actually in plain sight in the frame? 589 is the xrp riddle.
English
@encrypted_past @WhiteHouse Watching Jericho now. The intro to the first episode has a string of tones similar to the tone posted in the video 👀
English
Sarah Isberg retweetledi
FRAME 172-178 ANALYSIS: IT'S A PHONE SCREEN
_SiCk @ afflicted.sh | March 26, 2026
================================================================
WHAT PEOPLE ARE SAYING
================================================================
People are saying the horizontal banding in frames 172-178 of the
@WhiteHouse static video is a video. They're right. It's not glitch
art. It's not random interlacing. It's a phone screen capture with
display refresh sync artifacts.
Here's what the data shows.
================================================================
THE BANDING PATTERN
================================================================
Frame 172 (696x1280) contains 11 bright horizontal bands alternating
with dark regions. The bright bands break into two categories:
WIDE WHITE BANDS (near-uniform 255):
y=483-556 74px tall avg brightness 249.9
y=722-785 64px tall avg brightness 244.8
y=1211-1279 69px tall avg brightness 250.8
These three are nearly identical. Pixel diff between them is only
3-7. They're all capturing the same thing: a white background.
CONTENT BANDS:
y=0-57 57px tall HIGH horizontal variation (107)
y=586-609 24px tall
y=675-686 12px tall
y=816-839 24px tall
y=868-878 11px tall
y=1089-1122 34px tall
Band 1 (top, y=0-57) has the most actual image data. Brightness
varies across the width -- brighter in center, darker at edges.
Consistent with a status bar or app header being captured.
================================================================
THE DARK REGIONS AREN'T EMPTY
================================================================
This is the key finding. When you brighten the "black" areas between
bands by 20x, scattered rectangular pixel clusters appear at specific
coordinates. These aren't noise. They're positioned like UI elements.
Identified clusters:
y=82-92, x=563-575 small rectangle (UI element)
y=102-106, x=114-118 small rectangle (UI element)
y=112-128, x=682-695 RIGHT EDGE (scroll bar / chrome)
y=184-190, x=312-679 WIDE thin line (content separator)
y=226-230, x=481-494 small rectangle (button / icon)
y=258-278, x=640-695 RIGHT EDGE again
y=280-296, x=35-596 WIDE cluster (text line)
y=300-320, x=240-604 WIDE + BRIGHT (text / heading)
y=396-402, x=224-231 small rectangle
y=418-422, x=496-503 small rectangle
y=428-432, x=128-137 small bright cluster
y=440-446, x=466-478 small rectangle
y=458-464, x=656-666 RIGHT EDGE again
Pattern: small rectangular bright spots at specific positions,
plus repeating right-edge elements. This is what phone UI chrome
looks like when partially captured during a display refresh cycle.
Everything in the dark regions is monochrome (R=G=B), same as the
static noise in frames 1-163.
================================================================
ROW 302: THE SMOKING GUN
================================================================
Row 302 is the brightest content row in the dark regions. The pixel
profile across x=240-320:
x=240-248: brightness ramps up from 83 to 160, then drops (hump)
x=249-253: dips to 50-63 (gap between elements)
x=256-287: plateau at 180-185 (flat gray, ~32px wide)
x=288-302: drops to 149-157 (slightly darker gray)
x=303-316: SPIKE to 246-255 (pure white, 14px wide)
x=317-320: drops from 196 to 43 (sharp falloff)
That profile -- gray hump, gap, gray plateau, white spike, falloff --
is what anti-aliased rendered text or a UI button looks like on a
white background when captured at this resolution and brightness.
================================================================
WHAT THIS MEANS
================================================================
Frames 172-178 are a partially captured phone screen showing a
white-background app or webpage with UI elements. This is the same
phone used to capture the deleted "launching soon" video (boots,
projection on floor, "it's launching soon right?").
The video was assembled in GPAC 2.2.1:
Frames 1-163: Generated static noise (monochrome)
Frames 164-165: Jericho ASA flag insert (33ms subliminal)
Frames 166-171: Phone UI remnants (notification bar, status bar)
Frames 172-178: Phone screen capture (the app/page being previewed)
Frames 179-214: Return to static noise
Someone composited a phone screen recording into a generated static
video alongside a hidden secessionist flag. The phone screen shows
whatever "it" is that's "launching soon."
================================================================
WHAT WE NEED
================================================================
1. The original Post 1 video (deleted). If anyone has the raw .mp4
from X or Instagram (not a screen recording), it would show what
was being projected on the floor. The boots video and this screen
capture are from the same phone, same session.
2. Frames 166-171 at full resolution. The notification bar and status
bar remnants could identify the app that was open on the phone.
3. Someone to run frames 172-178 through neural super-resolution
(Real-ESRGAN / GFPGAN) to try to resolve the UI elements in the
dark regions into readable content.
================================================================
FILES IN THIS DUMP
================================================================
frame172_original_enhanced.png
Frame 172 as extracted, brightness already enhanced from your
original pull.
frame172_bright8x.png
Full frame with brightness multiplied 8x (same treatment as the
flag frame reveal).
frame172_dark_enhanced_20x.png
Full frame with brightness multiplied 20x. The hidden UI elements
in the dark regions become visible.
frame172_ui_elements_annotated.png
Frame at 8x brightness with red boxes marking the identified UI
element clusters in the dark regions.
frame172_hidden_content_map.png
Black canvas showing ONLY pixels above noise floor, brightened 20x.
The UI element pattern is visible without the bright bands
overwhelming the image.
frame172_content_region_enhanced.png
Extracted and enhanced view of the y=286-322, x=35-605 region
(the brightest content cluster in the dark area). This is the most
likely candidate for readable text/UI content.
frame172_visible_content.png
All rows with brightness above 25 extracted and stacked vertically.
749 of 1280 rows contain visible content.
frame172_comparison_strip.png
Side by side: original | 8x brightness | 20x brightness
frame172_statusbar_enhanced.png
Top 25 rows extracted and enhanced 5x. Possible phone status bar.
frame172_contentbar_enhanced.png
Rows 25-58 extracted and enhanced 3x. Content below status bar.
flag_frame_164_enhanced.png
The Jericho ASA flag from frames 164-165 for context. This is what
appears 8 frames before the phone screen capture.
_SiCk@encrypted_past
I pulled apart the @WhiteHouse video frame by frame. 214 frames, ~60fps, 3.6 seconds. Here's what's actually in it. The video was built with GPAC 2.2.1 (open source multimedia framework) before Twitter re-encoded it. Not a casual screen recording. The H.264 encoding has keyint=infinite and scenecut=0, meaning someone deliberately disabled keyframe insertion at scene transitions so you can't easily seek to the flag frames. That's intentional. Frames 1-163: Grayscale static. All three RGB channels are identical (pure monochrome noise). No LSB steganography detected in the frames Twitter's encoder left us, but re-encoding would destroy that anyway. Frames 164-165: The flag. When you brighten it 8x, it's a flag on a pole with VERTICAL red and white stripes and a blue star field. That's the Allied States of America flag from Jericho, a show about a shadow government nuking American cities and the country splitting apart. Two frames. Roughly 33ms of screen time. You'd never catch it at normal playback. Frames 166-171: Remnants of a phone UI. A notification bar strip at row 388 and a status bar at the top of frame. This thing was screen-captured from a phone. Frames 172-178: Horizontal banding pattern. Bright bands at irregular intervals across the frame. Not random noise. Looks like interlaced scan data from whatever source video was glitched up for the effect. Audio: iPhone notification chime starting at 2.26 seconds. Clean multi-harmonic tone. Spectrogram shows harmonics at ~1kHz, 2.5kHz, 5kHz, 7.5kHz, 10kHz, 12.5kHz. No hidden spectrogram images (Cicada 3301 style). No ultrasonic content. The Grok explanation that this is just a promo for the "Text USA to 45470" alert system doesn't explain why someone used GPAC to build a video with anti-seek encoding parameters and embedded a fictional secessionist flag from a nuclear apocalypse TV show in it. During an active military conflict. Whether this is an ARG, a psyop, or the most unhinged social media strategy in White House history, the Jericho flag was not an accident. Someone put it there on purpose.
English
Sarah Isberg retweetledi
@hodlrr17 I have been trying to figure out the Elvis connection. With all of this alien talk, Lilo and Stitch is coming to mind. Hawaii. Q Drop 1728
English
English
@thestoicplumber @WhiteHouse Sometimes you have to mix it up a lil bit
English