pikatorrent

Not sure who this is for? It looks like something made for casual users, but I'm not sure that they need a web UI for remote control or CLI. More advanced users are very unlikely to use something with such UI. I can't imagine that it will be fun to use while having 10 torrents, let alone 250+. Even Fragments[1], the GNOME Circle app for BitTorrent that targets casuals can fit more downloads in a single view. And what's the point of the search bar? All it does is open a new tab and search "torrent <keyword>" in either Google or DDG. I can do it myself. It's neither helping newbies nor advanced users. Also the 1.7M package-lock.json[2] scares me, but so do most JavaScript projects. Do we really need that many JS libraries for a UI for a BitTorrent client? In comparison, Transmission's web UI has a package-lock.json that uses 354K[3]. 1: htt

I find existing BitTorrent clients offer a rather old user interface, and it's hard to set up remote access, involving setting up a web server, a TLS certificate, domain name, configuring the router, etc... PikaTorrent tries to offer a modern and easy UI. It is available on desktop (Linux & Windows for now), mobile (Android for now), as CLI as an npm package, and even on the web (as a frontend for remote control). Thanks to WebRTC, one can link the mobile or web app with the desktop or CLI app. This way, it's possible to remotely manage torrents securely and without any complicated setup. From a technical point of view, the app is using Expo and Tamagui to target the web, desktop, and mobile (native), meanwhile libtransmission is used as the torrent engine. So we should expect the same level of performance as the Transmission client. Pika