News for hackers. Stuff that matters.
Re:Show HN: AutoShorts – Local, GPU-accelerated AI video pip... by rustyhancock on Sunday January 25, 2026 @05:06AM (#46752538)
I've started including a statement of AI usage in my docs.

HN is a niche audience but it seems like it's the first question everyone has when opening a repo.

Which is odd because the first question we should have is, does it work.

Personally I can't see myself ever writing the bulk of the README again, life's too short.

Re:Show HN: AutoShorts – Local, GPU-accelerated AI video pip... by divyaprakash on Sunday January 25, 2026 @06:08AM (#46753006)
Fair points all around. To be transparent: yes, I used an AI coding assistant (Antigravity) to help with the heavy lifting of refactoring the original legacy code and drafting the README. I’m with @rustyhancock on this—I’d rather focus my brainpower on the pipeline logic and hardware integration than on writing boilerplate and Markdown.

However, orchestrating things like decord with CUDA kernels, managing VRAM across parallel processes, and getting audio sync right with local TTS requires a deep understanding of the stack. An LLM can help write a function, but it won't solve the architectural 'glue' needed to make it a reliable CLI tool.

The project is open-source precisely because it’s a work in progress. It needs the 'human touch' for things like the RT-DETR auto-zoom and more nuanced video editing logic. PRs are more than welcome—I'd love to see where the community can push this beyond its current state.

Re:Show HN: AutoShorts – Local, GPU-accelerated AI video pip... by Hamuko on Sunday January 25, 2026 @06:12AM (#46753039)
I think my life's too short to ever read your READMEs.
Re:Show HN: AutoShorts – Local, GPU-accelerated AI video pip... by pelasaco on Sunday January 25, 2026 @11:05AM (#46755266)
The life ist too short to read AI generated README, which are clearly not written for humans..