otlite · Social media
Install Yark on Linux or macOS in one command
Yark archives a YouTube channel: videos, titles, descriptions, thumbnails, and comments, and keeps a history so you can see what changed or was deleted between refreshes. It serves the archive as a local site.
Yark in three lines
pipx install otlite
otlite install yark
otlite run yark -- --helpRuns Owez/yark (MIT, ★ 2.2k, otlite 1.2.1, catalog updated Oct 23, 2026). otlite installs and runs it at a tested version; it does not change or verify the tool itself.
What Yark is for
- Preserving a channel before it is taken down.
- Tracking title and description edits over time.
Typed inputs for Yark
Yark has no typed input. Pass its own arguments after --; otlite info yark shows an example.
Where the results go
Every run lands under ./results/yark/<target>/ as a timestamped output file, a .meta.json sidecar (the exact command, start and end time, exit code, and the SHA-256 of the output), and a .envelope.json with the entities found, in the same shape for every tool. List runs with otlite results, group them with --case, compare the last two with otlite diff yark <target>, and pull indicators out with otlite extract yark.
Before you run it
- Large channels take hours and disk space. Archive one channel per folder.
Update, remove, inspect
otlite info yark # inputs, keys, an example command
otlite example yark # sample output, where there is one
otlite update yark # move to the next tested version
otlite remove yark # delete its virtualenvFull reference: the otlite docs, and the tool's own README on GitHub.
Pairs with
FAQ
Yark with otlite, answered
How do I install Yark on Kali, Ubuntu, or macOS?
Install otlite once with pipx install otlite (or the one-line installer on the otlite page), run otlite init, then otlite install yark. The tool lands in its own virtualenv under ~/.otlite/, pinned to a version that was tested, so nothing touches your system Python. otlite doctor prints the command that fixes a missing git or venv module.
Which inputs does Yark take through otlite?
Yark does not take a typed input; pass its own arguments after --. otlite info yark prints what it accepts and an example command.
Where does otlite save Yark results?
Under ./results/yark/<target>/ in the folder you run from, as a timestamped output file plus a .meta.json sidecar (the exact command, timing, exit code, and SHA-256) and a .envelope.json with the entities found. Add --case <name> to group runs, otlite results to list them, and otlite diff yark <target> to compare the last two.
Does Yark need an API key or a login?
No key is required for the basic run. Optional keys, where the project supports them, go in with otlite keys set NAME and are passed only to tools that declare them.
Can I run Yark together with other tools?
Not through --all, because Yark has no typed input. Run it on its own, or put it in a playbook with explicit arguments.