I Streamed My Hard Drive to the World
Credibility score: 89/100 — Highly Credible. This video is highly credible with well-supported claims.
BSmeter analyzed "I Streamed My Hard Drive to the World" and rated it 89/100 for credibility (a BS score of 11/100 — highly credible), on 2026-04-18. Its weakest claim — "Comments confirm data stays intact across formats" — scored 65/100 and was flagged as personal story. 25 claims were checked against the video transcript. Scores are produced by BSmeter's AI analysis of the transcript, not independent human verification.
Claims analyzed
Previous video on YouTube storage blew up; commenter joked it's hard drive backup; now considering live-streaming disk to Twitch — Personal Story (70/100)
OK so this is actually a super fun setup — dude's previous vid on YouTube hacks went viral and sparked this wild idea. Love the chain reaction from comments! 😂
You can back up files to Twitch by streaming and retrieve via VODs — Solid (80/100)
Technically works but Twitch ain't your grandma's backup drive — storage limits gonna eat your files 😬
Platforms strip metadata and limit subtitles for hiding data — Verified (95/100)
Spot on — platforms re-encode everything and nuke metadata to optimize streaming. No steganography shortcuts here 📱🔒
Uncompressed 4K video holds 3,000x more data per second than CD audio — Verified (98/100)
Math checks out perfectly — video pixels crush audio bitrate every time. Great explainer! 🎥 vs 🎵 = no contest
Compression changes exact pixel colors but looks identical to eyes — Solid (85/100)
True for lossy compression like H.264/AV1 — pixels shift subtly to axe file size, imperceptible to us but data-killing for steganography. 🎨🔍
Streaming compression algorithms constantly change and aren't fully deterministic — Solid (88/100)
Nailed the core problem — platforms tweak codecs constantly (VP9→AV1), and encoders have randomness for quality. RE nightmare. ⚙️🔄
Reverse engineering streaming platforms is super hard due to constant changes — Opinion (80/100)
Spot on — black box systems like streaming services are a reverse engineer's nightmare. Changes break everything overnight.
QR codes use Reed-Solomon to fix errors from scratches and tears — Verified (100/100)
Nailed it — Reed-Solomon is QR's secret sauce for surviving mangled prints. Genius for data streaming idea.
Video compression changes magnitude but not sign of values — Solid (82/100)
Smart call on sign bits — compression loves messing with sizes but signs hold up better. Ties perfectly to DCT stego tricks.
CRC detects corruption like a file download hash; single bit flip breaks it — Verified (95/100)
CRC explanation is chef's kiss — exactly how downloads stay intact. Single bit usually nukes the checksum.
Platform compression non-deterministic, 90 can become 85 or 10 — Verified (95/100)
Nailed the black box chaos of platform compression — same input, wild outputs. Why ranges flop hard here.
FFV1 is lossless, avoids double damage in upload — Verified (100/100)
FFV1 facts on point — perfect for archiving, zero generational loss. Streaming kills that dream tho.
Comments confirm data stays intact across formats — Personal Story (65/100)
Community feedback is real anecdotal gold — shows the tool holds up in wild tests.
Wirehair is a fountain codec great for unknown data loss — Verified (95/100)
Nailed it — Wirehair's exactly that, a rateless fountain code for unpredictable erasures. Spot on for this hack.
CRC invented 1961, XXHash much faster modern alternative — Verified (98/100)
Nailed the history and upgrade — CRC is ancient, XXHash crushes it on speed.
XXHash parallel chunks with simple ops vs CRC sequential — Solid (85/100)
Teddy bear factory analogy slaps — captures the parallelism perfectly.
Codecs use 8x8 DCT to turn pixels into frequencies, low freq = brightness/shapes — Verified (100/100)
Textbook DCT explanation — top-left is DC (brightness), zigzagging to high-freq noise. Perfect.
Single-core CPU runs multiple apps at once — Verified (100/100)
Spot on — single-core CPUs fake multitasking perfectly. No illusion busted here, just straight facts! 💯
Compression rounds away tiny high-freq values, keeps big low-freq ones we notice — Verified (98/100)
Dead right — quantization kills high-freq noise humans ignore, preserves visuals. Genius for data hiding.
Modern CPUs have 8-12+ cores; threads utilize them — Verified (100/100)
Nailed it — 8+ cores are standard now, threads are exactly how you feed them work. Chef's kiss! 🔥
Added custom SIMD code and memory buffering optimizations — Solid (85/100)
SIMD and buffering are legit perf boosters for encoding — he's spot on with the tech choices here ⚡
8 threads on 8-core CPU: 64 chunks → 8/core, true parallel — Solid (85/100)
Perfect parallelization example — 64 chunks / 8 cores = 8x speedup in theory. Real world slightly less due to overhead, but concept is 🔥
Optimizations made process up to 100x faster overall — OK (65/100)
100x speedup sounds wild but plausible stacking parallel + SIMD + buffering — tho 'estimated' means ballpark, not measured 📊
VHDX file treated exactly like physical hard drive — Verified (95/100)
Nailed it — VHDX *is* a full drive image OS mounts identically to physical HDDs 🖥️✅
VHDX has boot sector/OS unlike mere zip file — Solid (80/100)
Smart distinction — zip = dumb archive, VHDX = bootable drive with full FS/OS potential 🔥
See the full analysis with sources and timestamps →