PicoTorrent

Torrent clients accumulate features until they contain a search engine, a feed reader, a media player and a web interface. PicoTorrent went the other way, shipping a list of transfers, a details pane and nothing else, in an application small enough to be measured in a handful of megabytes.

The PicoTorrent engine underneath is the same library the well-known clients use, so protocol behaviour, speed and peer handling are not where it differs. Everything above that library is what was cut.

That includes support for the newer version of the protocol, alongside the original and the hybrid form that carries both, which arrived here earlier than in several larger clients.

What was deliberately left out

The PicoTorrent omissions are the product, so they deserve listing rather than glossing over.

No search facility, so finding something to download happens in a browser. No feed reader, so automatic downloading from a subscription is not possible. No web interface, so the client cannot be driven from another machine or a phone.

Each of those is a feature people use, and each is also code running in an application exposed to data from strangers. A client that cannot fetch and parse a feed cannot be attacked through one, which is the argument the minimal approach makes.

Whether that trade appeals depends entirely on which of those features you actually use. Somebody who drives everything from feeds loses the whole workflow, and somebody who clicks a link occasionally loses nothing.

For the same engine with all of those features present and a conventional interface, qBittorrent is the client the community recommends by default.

The missing library error

Here is the practical PicoTorrent obstacle people meet, and it produces an error that explains nothing.

One build expects a common runtime component to be present on the machine and does not carry it, so on a system lacking it the application refuses to start, reporting a missing library.

Most machines have that component already, put there by something else, which is why the failure appears random from one computer to the next.

Knowing that turns a five-second fix into a five-second fix rather than an afternoon of assuming the download was faulty.

Development stopped, and that matters more here

Being direct about the decisive fact.

PicoTorrent has not been updated for a long time, and directories that track such things list it as discontinued.

For most abandoned software that means missing features and eventual incompatibility. For a network client it means something sharper, because this is an application that connects to strangers and parses whatever they send it. The library underneath has continued to receive fixes that this build does not have.

That is the honest reason to look elsewhere despite the design being sound. The minimal attack surface argument was a good one, and it assumed the code was current.

For a client from a different lineage with its own engine and a similarly restrained interface, a maintained alternative that avoids the shared library entirely is still being developed.

What you download is your responsibility

Briefly, because it belongs in any honest PicoTorrent description.

The protocol is a distribution method, used deliberately for operating system images, large scientific datasets, archival collections and game updates, because it moves large files to many people efficiently.

A client transfers whatever you point it at. Whether a particular transfer is lawful depends on its contents and the rights you hold, which is a question about your choices rather than about the software.

For a client built around running the transfers on a machine that stays on, rather than the one in front of you, Deluge separates the two halves.

Conclusion

PicoTorrent made an argument worth making, which is that a torrent client should transfer torrents and nothing else. Stripping out the search engine, the feed reader and the web interface produced something small, quick and native, with less code exposed to whatever peers send it.

The argument has outlived the software. A network client that has not been updated in years no longer benefits from a small attack surface, because the surface it has is unpatched, and the engine beneath it has moved on. Admire the design, and install something that is still being looked after.