Urgent.News

What's breaking now, across thousands of outlets.

Tech

99.98% blocked: I ran 9,000 Shorts through my filter so the old model could fail in peace

I built this filter because my own Shorts feed had become unusable — scammy re-uploads, AI slop loops, and clickbait compilations stacked ten deep. I wanted numbers, not vibes, so I pulled 9,000 Shorts and scored them against two classifiers: the current one and the previous revision I still had deployed. The old model let 8,667 of the 9,000 through. That's a 96.3% miss rate, and it explains…

A journalist built a filter to combat scammy re-uploads, AI slop loops, and clickbait compilations that were clogging up their own Shorts feed. They ran 9,000 Shorts through two classifiers: the current model and an older revision still in use. The previous model allowed 8,667 of the 9,000 videos through, resulting in a 96.3% miss rate and explaining their recent frustration with the feed's quality.

The new model, however, blocks 99.98% of the videos. The mechanism behind this high blocking rate involves sampling 8 frames per video, hashing them, and deduplicating near-identical frames across the entire collection before they reach the model. This preemptive step eliminates most mass-reupload spam. The filtered videos then undergo a transcript-plus-visual embedding pass, and any entries under the confidence threshold are blocked rather than merely demoted.

The latter approach ensures that junk content remains in a "maybe" queue where humans can still identify and address it. The operator's costs are roughly 40 GPU-minutes per 1,000 videos during the frame-sampling phase, along with storage for the hashes. Skipping the dedupe step would nearly triple the operating costs for the same level of blocking.

The journalist has detailed the entire process, including per-class breakdowns and the old model's failure cases, in a YouTube Shorts video available at https://www.youtube.com/shorts/oZmarp6b8Qw.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Idempotency Keys and Distributed Transactions Prevent Double Payouts During Network Timeouts

The Anatomy of a Cross-Border Phantom Payout When an application client initiates a cross-border transfer, it projects an illusion of atomicity—a single, monolithic API request that cleanly moves…

  • Double payouts during network timeouts stem from distributed transaction complexity.
  • Idempotency keys with status inquiries prevent duplicate payouts in transient network partitions.
  • Circuit breakers are needed when partner systems are down or inconsistent.

Building Digital Healthcare Experiences: Telemedicine, Doctor Profiles, and Appointment Systems

Healthcare applications are an interesting example of how software engineering can address real-world problems. Patients need convenient ways to discover doctors, arrange appointments, and communicate…

  • Telemedicine enables remote communication between patients and doctors.
  • Doctor profiles present essential information for patient decision-making.
  • Appointment systems facilitate convenient access to healthcare services.

More from Saturday 14 November →