What we learned clipping 156 security talks

The run in numbers

One job per talk, all with the same settings: 9:16 clips of 30 to 60 seconds. The run was August 15, 2026.

How long it took

We submitted 146 of the talks, 71 hours of video, at once. Half were done after 2.7 hours and the last finished after 5.4. Measured per job, the median was 12.5 minutes of processing per hour of video.

Where the time goes surprised us. Hearing every word is the expensive part: transcription took 39% of the processing time and cutting and reframing 36%. Captions took 10%. Choosing the moments, the part that looks like magic, took 3%.

What it picked

• Live demos that pay off: a master key found, a trading bot that works.
• Stories with an ending.
• Strong opinions said plainly.
• Shorter talks are denser: under 15 minutes gave about 17 clips per hour, over 90 minutes about 7.
• Most picks come early: 56% start in the first 30% of a talk, and under 3% in the last tenth, where questions from the audience usually are.

Ten moments it found

We made each one into a Short for our channel, posted or scheduled this week. To see the whole talk, check it out here: every link opens the full talk on YouTube at the moment the clip starts.

• $5 buys a browser extension, and everyone who installed it · "One Click Compromise", tuckner
• A master key system decoded: right off the bat, it opens · "Privilege Escalation in Mechanical Master-Key Systems", Arden Meyer
• 39 days of an AI agent trading RuneScape's Grand Exchange · "Defeating the Grand Exchange", Chase Phelps
• The hard part of an AI romance scam: not acting like a bot · "Love, Lies, and Lures", Stephanie Carruthers and Matt Bangert
• Give an AI agent your file system and bad things can happen · "applIDE ai", Dusty Evanoff
• Who is really behind most criminal hacking · "Mythos", Bryson Bort
• Suspended on purpose, to go home and read about computers · "Grifter Being Grifter", Grifter
• Planes report their GPS position on 1090 MHz: ADS-B explained · "Infiltrate Radio", Noah Dunker and friends
• You could be up here giving this talk · "So you wanna build a Security Lab?", Gared Seats
• Don't count on a degree to get into hacking · "Make Your Own Way, Or Help Someone Do It", Zach Hilbert

Watch four of them

The clips exactly as legit2clip cut, framed and captioned them, posted as Shorts. Each Short links back to the speaker's full talk.

What went wrong, and what we changed

• Downloading was a lottery. YouTube blocks data-center addresses, so we fetched the archive from a home connection. The first pass got 83 of 157 talks. Retrying fixed most of the rest, often with the exact settings that had just failed. Lesson: retry before you re-engineer.
• Waiting in line counted as working. 84 of the 156 jobs hit their time limit at least once because the clock started while they were still queued. Every one of them finished on its automatic retry.
• Neighbouring clips shared footage. In this run 34% of clips repeated a few seconds of the clip next to them (median 15 seconds). Since October, no sentence ever lands in two clips.
• Transcription ran out of memory. Every worker loaded its own speech model, and on smaller graphics cards that spilled over and ran 20 to 30 times slower. Now each machine runs one model sized to fit it.
• The framing didn't follow the speaker. In August a vertical crop sat at one average position. Real face tracking arrived at the end of August.
• Scores are relative, not grades. The same moment scored 99 in one run and 27 in another. Within a talk the ranking holds up; across runs the numbers don't. We're reworking how the score threshold decides how many clips a talk gets.

Thank you, SecKC

SecKC is Kansas City's hacker meetup, and it puts its talks on YouTube. They let us use the archive to test, and every clip we post links back to the speaker's full talk.