Original Summary

Most torrent workflows look like this: open a browser, search five different sites, squint at seeder counts across tabs, copy a magnet link, open another app to actually download it, then open yet another app to watch it. I wanted that whole thing to live in one terminal window. That's what Tornedo is. One search hits every indexed source at once. Results get merged, de-duplicated, and ranked automatically, so there's no more manually comparing the same release across three sites. Release titles get parsed into actual metadata (quality, codec, season/episode, etc.) instead of you reading raw filenames. And if you don't want to download at all, you can search and stream movies, TV, and live TV directly, with playback in mpv/VLC/IINA, subtitles, and resume built in. Beyond that: Pick individual files before a download starts Interrupted downloads recover automatically, pieces re-verified tornedo doctor diagnoses config, network, and source issues Full TUI or pure command line, your choice Built on Ink + React for the interface, plain Node.js underneath. No Electron, no browser runtime hiding in there. I didn't set out to solve "how do you download a torrent," that part was never the hard problem. The actual question was: how do you make searching, comparing, watching, and managing torrents feel like something that belongs in a terminal, instead of a workaround bolted onto one? Curious what CLI/TUI regulars think is missing or if I can add something more. GitHub: https://github.com/Itshardtofindagoodname/Tornedo npm: https://www.npmjs.com/package/tornedo   submitted by   /u/Sno_w_olf [link]   [comments]

  • 情报分类：工作与职业机会
  • 分类依据：内容涉及招聘、求职或职业发展
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/23 06:24:51