From Bibliotheca Anonoma

Home Servers work perfectly as a Torrent Seedbox, as it is always on.

Torrent Client[edit]

Since all Linux torrent clients use libtorrent at their core, base performance will be similar. However, each client brings with it special features that can increase CPU or memory usage, so choose the client that fits the strength of your seedbox.

From this performance chart, most torrent clients will consume less than 80MBs of RAM.

  • Transmission - Best lightweight torrent client, ideal for the Raspberry Pi. A bit lightweight on features, but good enough for the basics and easy to install.
  • Install
  • Change Username/Password
  • rtorrent + rutorrent - rtorrent is a command-line based torrent client with a huge load of features. rutorrent is a Web interface for rtorrent, which presents all options in a charming GUI. However, it can be very difficult to install and configure, and consumes slightly more processing power than Transmission.
  • Deluge - A good balance of features and weight over Tranmission. If you can definitely spare 50MBs of RAM, this is what you want. Easy to install.
  • QBittorrent - A uTorrent-style client for Linux.


For Deluge, you should provide two means of access: the WebUI, and the Deluge Thin Client. The WebUI can be accessed in the web browser, while the Thin Client uses a deluge program on the client for more effective configuration.

Also, if you want to have the core Deluge daemon run on a different port, edit ~/.config/deluge/core.conf (for the user running the daemon, usually deluge) and change as necessary. You will also have to set this port on the WebUI's Connection Manager next time you access it.

Quick and easy setup script (Debian):

CentOS instructions:


Usually, the only way DMCAs can be issued against torrent peers is by connecting to the network and recording every single IP address.

One way to combat this is to install a public blacklist, which refuses to connect to peers associated with DMCA-issuing activity.

Torrent Encryption[edit]

If your ISP is deliberately slowing down, scanning, or blocking torrents, you can obfuscate torrent data by enabling encryption. It takes up more CPU power, and needs a bit more time, but that's nothing compared to throttling.

Transmission generally prefers peers with encryption enabled, but you can require peers to have it.

Note: This does not anonymize or hide your IP Address! If that is necessary, you will need a good VPN that allows torrents.


Creating Torrents with Transmission-cli[edit]

Sometimes you will need to send large files from a server. However, this is no small feat without a graphical interface.

Key to this method is using the transmission daemon. Remember, to use it with Transmission-remote you need the username and password given using the option -n. Here's a script that will set you up (using the default password):

cp -p $1 $TRANSDIR/downloads/
transmission-create $TRANSDIR/downloads/$1 -t udp:// -o $HOME/$1.torrent
transmission-remote -n transmission:transmission --add $HOME/$1.torrent


Create and Share tons of data with Torrents[edit]

Torrents are the most reliable way to transmit large amounts of data. All items are checksummed, you can stop and continue anytime and if there are a lot of people downloading, that simply increases the download speed.

mktorrent -a -o my-really-long-novel.torrent my-really-long-novel.pdf

You will want to use an open tracker to seed.

Torrent Subscriptions[edit]

YaRSS 2 + Deluge Method[edit]

This is the preferred method by ShanaProject. Connect to Khartov via using a Deluge Thin Client (the windows program) via the default port.

FlexGet Method[edit]

This is another way to do it, and is compatible with other RSS feeds.

  1. Set up FlexGet with ShanaProject or other RSS feeds.
  2. Set up FlexGet to put .torrent files in a watchdir when a show appears.
  3. Set up Deluge to check the watchdir for any new torrent files, and download them.