Escrow Security for iCloud Keychain
6 by gurjeet | 0 comments on Hacker News.
Saturday, 25 April 2026
Friday, 24 April 2026
Thursday, 23 April 2026
Wednesday, 22 April 2026
Tuesday, 21 April 2026
New top story on Hacker News: Show HN: VidStudio, a browser based video editor that doesn't upload your files
Show HN: VidStudio, a browser based video editor that doesn't upload your files
8 by kolx | 0 comments on Hacker News.
Hi HN, I built VidStudio, a privacy focused video editor that runs in the browser. I tried to keep it as frictionless as possible, so there are no accounts and no uploads. Everything is persisted on your machine. Some of the features: multi-track timeline, frame accurate seek, MP4 export, audio, video, image, and text tracks, and a WebGL backed canvas where available. It also works on mobile. Under the hood, WebCodecs handles frame decode for timeline playback and scrubbing, which is what makes seeking responsive since decode runs on the hardware decoder when the browser supports it. FFmpeg compiled to WebAssembly handles final encode, format conversion, and anything WebCodecs does not cover. Rendering goes through Pixi.js on a WebGL canvas, with a software fallback when WebGL is not available. Projects live in IndexedDB and the heavy work runs in Web Workers so the UI stays responsive during exports. Happy to answer technical questions about the tradeoffs involved in keeping the whole pipeline client-side. Any feedback welcome. Link: https://ift.tt/ApCDW4a
8 by kolx | 0 comments on Hacker News.
Hi HN, I built VidStudio, a privacy focused video editor that runs in the browser. I tried to keep it as frictionless as possible, so there are no accounts and no uploads. Everything is persisted on your machine. Some of the features: multi-track timeline, frame accurate seek, MP4 export, audio, video, image, and text tracks, and a WebGL backed canvas where available. It also works on mobile. Under the hood, WebCodecs handles frame decode for timeline playback and scrubbing, which is what makes seeking responsive since decode runs on the hardware decoder when the browser supports it. FFmpeg compiled to WebAssembly handles final encode, format conversion, and anything WebCodecs does not cover. Rendering goes through Pixi.js on a WebGL canvas, with a software fallback when WebGL is not available. Projects live in IndexedDB and the heavy work runs in Web Workers so the UI stays responsive during exports. Happy to answer technical questions about the tradeoffs involved in keeping the whole pipeline client-side. Any feedback welcome. Link: https://ift.tt/ApCDW4a
Subscribe to:
Comments (Atom)