IdeaWell

Project ideas from Hacker News discussions.

Show HN: VidStudio, a browser based video editor that doesn't upload your files

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

1. LGPL compliance for browser‑based apps

  • Key point: The LGPL obliges you to let users replace the LGPL component, which is tricky when the whole app is a single WebAssembly blob.

    “LGPL permits you to distribute binaries, but you can't distribute the software as an opaque binary blob with no reasonable way to modify it.” – elpocko

  • Additional requirements: Provide source links, allow swapping the library, and supply tools for relinking or replacement.

    “User must be able to replace the LGPL library with his own version of the library.” – actionfromafar

2. Open‑source vs. commercialization debate

  • Many commenters see releasing the code (or at least an adapter) as the cleanest way to avoid licensing trouble and to gain community goodwill. > “Any reason not to just open source it? … IMHO AGPL would be a good fit here as it complies with LGPL and also ensures nobody besides you (the copyright holder) can stand it up for profit without contributing back.” – freedomben - Others note that commercialisation is possible, but only if you respect the copyleft terms; otherwise you risk infringement.

    “The problem is you can commercialise free software if you're creative about it.” – mghackerlady

3. Technical hurdles of client‑side video editing

  • Implementing demuxing, format support, and performance is non‑trivial; issues like 10‑bit video, audio codec limits, and per‑frame decoder re‑initialisation affect user experience.

    “It should be possible to comply with LGPL without publishing the source code of the whole application. Either by running the application and ffmpeg in different isolates (wasm processes), or by offering a way to merge (link) the wasm code of the closed‑source application with a user compiled FFmpeg wasm build.” – sroussey

  • Practical concerns include handling varied container formats, maintaining decoder state, and supporting features such as 10‑bit video or subtitles.

    “I could not import 10‑bit video on Windows which I think would be fairly common among the target audience.” – prhn

These three themes—LGPL compliance, the open‑source/commercial tension, and the technical complexities of pure‑client video editing—capture the bulk of the discussion.

🚀 Project Ideas

LGLP‑WasmAdapters

Summary

  • Provides a developer SDK that automatically splits FFmpeg WebAssembly into isolated modules that can be swapped by users, ensuring LGPL compliance without manual legal work.
  • Guarantees replaceable modules and auto‑generates source‑distribution links for compliance.

Details

Key Value
Target Audience Web developers building client‑side media editors or encoders that use FFmpeg or other LGPL codecs.
Core Feature Auto‑generates separate WASM isolates per codec, injects runtime swapping hooks, and produces a compliance manifest with source URLs.
Tech Stack Rust/Wasm compilation, TypeScript wrapper, Node.js CLI for manifest generation, React UI for integration.
Difficulty Medium
Monetization Revenue-ready: SaaS subscription per active project ($15/mo)

Notes

  • HN users repeatedly emphasized the need for a clear way to replace LGPL libraries in browser apps (e.g., “User must be able to replace the LGPL library with their own version of the library”). This tool directly addresses that requirement and the licensing anxiety voiced by elpocko and prhn.
  • By handling the isolation and source‑distribution steps automatically, developers can ship closed‑source editors while staying compliant, removing the friction that prevents many from offering client‑side video tools.

Open‑Core Privacy‑First Video Editor (Freemium)

Summary

  • A fully client‑side video editor that runs all decoding/encoding locally, with an optional paid extension pack that adds premium codecs, advanced effects, and cloud‑free collaboration; source code of the core editor is open‑sourced under MIT for compliance.
  • Solves the demand for no‑upload editors while providing a sustainable revenue stream.

Details

Key Value
Target Audience Hobbyist and semi‑professional creators who need private editing but are willing to pay for premium features.
Core Feature Core editor (open source) + modular extension marketplace; paid extensions are delivered as separate WASM bundles that can be swapped without re‑upload.
Tech Stack PixiJS for rendering, WebCodecs API, FFmpeg.wasm isolates, Jest tests, GitHub Actions CI.
Difficulty High
Monetization Revenue-ready: Tiered subscription ($9/mo basic, $29/mo pro) plus one‑time extension purchases

Notes

  • Discussion highlighted the attractiveness of privacy‑first tools (“No accounts and no cloud a lot!”) yet scarcity of viable business models. This project supplies that model while staying LGPL‑compliant via open‑source core and clearly separable extensions, directly mirroring the “Closed source is fine… but you must provide replacement mechanisms” concerns.

--- ## Browser‑Based Transcode‑as‑Service Platform (Compliance‑First)

Summary- A hosted API that processes user‑uploaded media entirely in the browser using isolated WebAssembly workers for each LGPL component, guaranteeing replaceability and providing automatic source‑distribution links.

  • Monetizes via pay‑per‑export credits while ensuring full licensing compliance.

Details| Key | Value |

|-----|-------| | Target Audience | Developers of lightweight web apps that need on‑device transcoding but want to avoid licensing pitfalls. | | Core Feature | Client‑side wrapper launches separate WASM workers for each codec; each worker includes a manifest linking to a publicly accessible source tarball of the used LGPL library version. | | Tech Stack | Service Workers, Deno runtime for worker orchestration, TypeScript, Docker for CI testing, Stripe for credit purchases. | | Difficulty | Medium | | Monetization | Revenue-ready: 0.01 USD per minute of processed video |

Notes

  • The HN thread repeatedly asked how to legally ship closed‑source editors using FFmpeg in the browser (e.g., “How does it compare to other tools?” and “Any reason not to just open source it?”). This service abstracts the compliance burden away from developers, offering a frictionless way to comply while earning revenue per export, directly answering the community’s call for practical, monetizable, compliant solutions.

Read Later