Run SHA-256 as WebAssembly with JS fallback; note ffmpeg.wasm as deferred
This commit is contained in:
@@ -32,3 +32,13 @@ yt-dlp (or an equivalent extractor) on the phone's own IP, checks the server
|
||||
cache first, then uploads the finished file in the background through the
|
||||
device intake (`POST /api/p2p/intake`, `server/p2p-intake.js`). The server's
|
||||
yt-dlp stays as the fallback when the device fails.
|
||||
|
||||
## Client-side video editing with ffmpeg.wasm (deferred 2026-10-02)
|
||||
|
||||
Skipped on purpose. ffmpeg.wasm is about 25–30 MB, and fast (multi-threaded)
|
||||
use needs cross-origin isolation (COOP/COEP). That would break the YouTube
|
||||
thumbnails and avatars unless every image host sends CORP headers, and we do not
|
||||
control `i.ytimg.com` / `ggpht.com`. The server already trims video (edit & download
|
||||
runs ffmpeg there), so the browser gains nothing it needs. Revisit only if offline
|
||||
editing becomes a requirement; then load it lazily from a worker and measure the
|
||||
isolation fallout first.
|
||||
|
||||
Reference in New Issue
Block a user