Group items tagged

08/31/08 12:55:48 changed by josef ¶ I've written a patch to support magnet links now. You need to check out svn rev 1065 of libtorrent/rtorrent, and get http://ovh.ttdpatch.net/~jdrexler/rt/experimental/dht-pex-static_map.diff and http://ovh.ttdpatch.net/~jdrexler/rt/experimental/magnet-uri.diff then in the directory that has the libtorrent and rtorrent subdirs you've checked out, do patch -p0 < dht-pex-static_map.diff patch -p0 < magnet-uri.diff and recompile both. It uses the official magnet protocol from Bittorrent BEP-0009 which is incompatible with Azureus and so far only supported by uTorrent 1.8+, so it'll only work if there are recent uTorrents in the swarm. It supports magnet links in both the old style base32 encoded hashes as well as the recommended URL-encoded hashes. Note that if there is one or more tracker URLs to use for the download, it must be present as "tr=..." argument in the magnet URI, because there is currently no way of adding trackers in rtorrent afterwards, so without that it'll use DHT and nothing else. After opening a magnet URI, it will add a meta download to download the actual torrent info. When that is complete, it is replaced by the real torrent. The meta data is saved in your standard torrent download directory, you can delete that after the real torrent has appeared, or you can keep it in case you need to open the same magnet URI again.

SRTP usually, ZRTP less often, and VOIP over VPN least often. As long as both sides of the connection support SRTP or ZRTP and are configured to kick it in as needed, usually all I do is check for the lock icon.

Any clients which support OTR should be encrypted easily. Adium is pretty standard on OS X; Pidgin or Miranda work fine on the Windows end. And if the other person doesn't support OTR, the system falls back to unencrypted.