Technically the project evolved too. At first it used crude frame differencing: identify a static rectangle, blend surrounding pixels, and hope. That worked for DVDs and ancient camcorder logos, but failed spectacularly on modern, animated marks. So Mina added intelligent inpainting models—lightweight, privacy-conscious neural networks trained on synthetic watermarks and non-copyrighted footage. The models ran locally, and the CLI offered presets: “restore home video,” “educational reuse,” and “archive cleanup.” A careful mode preserved subtle artifacts when requested, so restorers could keep historical fidelity rather than producing a glossy, untraceable fake.
There was a forgotten corner of the internet where old tutorials and abandoned projects drifted like shipwrecks—GitHub repositories with brittle READMEs, half-finished scripts, and commit histories that whispered about better days. Among them, a tiny repo called watermark-better lay unstarred, its purpose simple and controversial: remove watermarks from videos. video watermark remover github better
Contributors arrived with expertise. An archivist from a regional museum documented how logos often reveal historical provenance and why metadata should be preserved; she helped add a “meta-preserve” flag that exported removed watermark regions as separate image layers alongside the cleaned video. A lawyer contributed a short template license and an automated warning: when the tool detected prominent brand marks, it would ask the user to confirm legal ownership before proceeding. The project’s issues transformed into polite debates about what “better” meant: better code, better ethics, or better outcomes for communities who’d been abandoned by corporate platforms. Technically the project evolved too
Years later, watermark-better wasn’t the biggest or flashiest repo on GitHub, but it had become a model of a different kind of open-source success: one that combined technical care with ethical guardrails. Mina moved on to other projects, but she left the repo with a clear mission statement and maintainers who took stewardship seriously. The codebase had a README that read less like a command manual and more like a small handbook for responsible restoration: how to verify ownership, how to keep provenance, and when to walk away. Among them, a tiny repo called watermark-better lay