Deluge (software)
 | |
|
Screenshot of Deluge downloading a torrent | |
| Developer(s) | Andrew Resch, Damien Churchill, John Garland |
|---|---|
| Initial release | September 25, 2006 |
| Stable release | 1.3.13 (July 20, 2016) [±] |
| Preview release | None [±] |
| Written in | Python |
| Operating system | FreeBSD, Linux, Mac OS X, Windows |
| Type | BitTorrent client |
| License | GNU GPL v3 |
| Website |
deluge-torrent |
Deluge is a BitTorrent client written in Python. Deluge is cross-platform, using a front and back end architecture where libtorrent, a software library written in C++ which provides the application's networking logic, is connected to one of various front ends (including a text console, a Web interface, and a graphical desktop interface using GTK+) through the project's own Python bindings.
Released under the terms of the GNU General Public License, Version 3, Deluge is free, open source software.
Features
Deluge aims to be a lightweight, secure, and feature-rich client.[1][2][3] To help achieve this, most of its features are part of plugin modules which were written by various developers.
Starting with version 1.0, Deluge separated its core from its interface, running it instead in a daemon (server/service), allowing users to remotely manage the application over the web.[4] Deluge has supported magnet links since version 1.1.0 released on January 2009.[5]
History
Deluge was started by two members of ubuntuforums.org, Zach Tibbitts and Alon Zakai, who previously hosted and maintained the project at Google Code, but who subsequently moved it to its own website.
In its first stages, Deluge was originally titled gTorrent, to reflect that it was targeted for the GNOME desktop environment. When the first version was released on September 25, 2006, it was renamed to Deluge due to an existing project named gtorrent on SourceForge, in addition to the fact that it was finally coded to work not only on GNOME but on any platform which could support GTK+.[6]
The 0.5.x release marked a complete rewrite from the 0.4.x code branch. The 0.5.x branch added support for encryption, peer exchange, binary prefix, and UPnP.
Nearing the time of the 0.5.1 release, the two original developers effectively left the project, leaving Marcos "markybob" Pinto and Andrew "andar" Resch to continue Deluge's development.
Version 0.5.4.1 saw support for both Mac OS X (via MacPorts) and Windows being introduced.
Around this time, Deluge became notable for its resistance to Comcast's bandwidth throttling without a change in code, while clients like Vuze (Azureus) and μTorrent had to borrow the method implemented by Deluge.[7]
From version 1.1.1 through version 1.1.3, Windows installers were temporarily unavailable due to the Windows packager leaving the project.
Following 1.1.3, packages for all non-Windows operating systems are no longer provided by the developers; instead, source tars and community provided packages were released.
See also
References
- ↑ Kereki, Federico (December 27, 2007). "After torrents? Try Deluge!". Linux.com. SourceForge, Inc. Archived from the original on 2009-05-31. Retrieved December 10, 2010.
- ↑ enigmax (June 14, 2007). "Deluge Torrent Client Aims to Thwart ISP Traffic Shaping". TorrentFreak. Retrieved December 10, 2010.
- ↑ Wong, Chin (November 9, 2009). "Good Karma". Digital Life. Retrieved December 10, 2010.
- ↑ andar (September 28, 2008). "Deluge 1.0.0 - "Sharks Are Bulletproof" Released!". Deluge. Retrieved December 10, 2010.
- ↑ "Deluge 1.1.0_RC/ChangeLog" (plain text). Deluge. June 15, 2009. Retrieved December 10, 2010.
- ↑ Ty (September 26, 2006). "gTorrent becomes Deluge: Version 0.1.0 Released". Deluge. Ubuntu Forums. Retrieved December 20, 2010.
- ↑ amc1 (January 3, 2008). "Re: Better encryption". uTorrent.com. p. 4. Retrieved December 10, 2010.
If there's anyone out there willing to help - we (Azureus devs) worked with alus to see what Deluge was doing differently to avoid being throttled... we've made changes as well, but we don't have anyone to test with. So if there's anyone who belongs to one of the affected ISPs, and they're willing to spend a few minutes helping us test our changes, that'd be appreciated.