LimeWire

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
LimeWire
File:Limewire logo.gif
Developer(s) Lime Wire LLC
Initial release May 3, 2000; 24 years ago (2000-05-29-26)
Last release 5.5.16 / October 26, 2010; 14 years ago (2010-10-26)
Preview release 5.6.1 / May 7, 2010; 14 years ago (2010-05-07)
Written in Java
Platform Cross-platform
Available in 32 languages
Type Peer-to-peer file sharing
License GNU General Public License
Website www.limewire.com closed (seized) in 2010[1]

LimeWire was a free peer-to-peer file sharing (P2P) client program that ran on Windows, Mac OS X, Linux, and other operating systems supported by the Java software platform.[2] LimeWire used the gnutella network as well as the BitTorrent protocol.[3] A freeware version and a purchasable "enhanced" version were available. BitTorrent support is provided by libtorrent.

On October 26, 2010, U.S. federal court judge Kimba Wood issued an injunction forcing LimeWire to prevent "the searching, downloading, uploading, file trading and/or file distribution functionality, and/or all functionality" of its software in Arista Records LLC v. Lime Group LLC.[4][5] A trial investigating the damages necessary to compensate the affected record labels was scheduled to begin in January 2011.[6] As a result of the injunction, LimeWire stopped distributing the LimeWire software, and versions 5.5.11 and newer have been disabled using a backdoor installed by the company. However, version 5.5.10 and all prior versions of LimeWire remain fully functional and cannot be disabled unless a user upgrades to one of the newer versions.[7][8] The program has been "resurrected" by the creators of WireShare (formerly known as LimeWire Pirate Edition).[9]

Features

Written in the Java programming language, LimeWire is able to run on any computer with a Java Virtual Machine installed. Installers were provided for Apple's Mac OS X, Microsoft's Windows, and Linux. Support for Mac OS 9 and other previous versions was dropped with the release of LimeWire 4.0.10. From version 4.8 onwards, LimeWire works as a UPnP Internet Gateway Device controller in that it can automatically set up packet-forwarding rules with UPnP-capable routers.

LimeWire offers sharing of its library through the Digital Audio Access Protocol (DAAP). As such, when LimeWire is running and configured to allow it, any files shared are detectable and downloaded on the local network by DAAP-enabled devices (e.g., Zune, iTunes). Beginning with LimeWire 4.13.9, connections can be encrypted with Transport Layer Security (TLS). Following LimeWire 4.13.11, TLS became the default connection option.[10]

Version history

Until October 2010, Lime Wire LLC, the New York City based developer of LimeWire, distributed two versions of the program: a basic free version, and an enhanced version, LimeWire PRO, sold for a fee of US$21.95 with 6 months of updates, or $34.95 with 1 year of updates.[11] The company claimed the paid version provides faster downloads and 66% better search results. This is accomplished by facilitating direct connection with up to 10 hosts of an identical searched file at any one time, whereas the free version is limited to a maximum of 8 hosts.[12]

LimeWire 2

Being free software, LimeWire has spawned forks, including LionShare, an experimental software development project at Penn State University, and Acquisition, a Mac OS X-based gnutella client with a proprietary interface. Researchers at Cornell University developed a reputation management add-in called Credence that allows users to distinguish between "genuine" and "suspect" files before downloading them. An October 12, 2005 report states that some of LimeWire's free and open source software contributors have forked the project and called it FrostWire.[13]

LimeWire was the second file sharing program after Frostwire to support firewall-to-firewall file transfers, a feature introduced in version 4.2, which was released in November 2004. LimeWire also now includes BitTorrent support, but is limited to three torrent uploads and three torrent downloads, which coexist with ordinary downloads. LimeWire 5.0 added an instant messenger that uses the XMPP Protocol, an open source communication protocol. Users can now chat and share files with individuals or a group of friends in their buddy list.

A screenshot of Limewire 5 0 11 beta

From version 5.5.1, LimeWire has added a key activation, which requires the user to enter the unique key before activation the "Pro" version of the software. This has stopped people from illegally downloading the "Pro" versions. However, there are still ways to bypass this security feature, which was done when creating the pirate edition. For example, there are currently cracks available on the internet, and people can continue using the LimeWire Pro 5.5.1 Beta, which also includes AVG for LimeWire and is the first version to include AVG. The most recent stable version of LimeWire is 5.5.16.

Versions of LimeWire prior to 5.5.10 can still connect to the Gnutella network and users of these versions are still able to download files, even though a message is displayed concerning the injunction during the startup process of the software. LimeWire versions 5.5.11 and newer feature an auto-update feature that allowed Lime Wire LLC to disable newer versions of the LimeWire software. Older versions of LimeWire prior to version 5.5.11, however, do not include the auto-update feature and are still fully functional. As a result, neither the Recording Industry Association of America (RIAA) nor Lime Wire LLC have the ability to disable older versions of LimeWire, unless the user chooses to upgrade to a newer version of LimeWire.[8]

Limewire 2008

On November 10, 2010, a secret group of developers called the "Secret Dev Team" sought to keep the application working by releasing the "LimeWire Pirate Edition".[14] The software is based on LimeWire 5.6 Beta, and is aimed to allow Windows versions to still work and remove the threat of spyware or adware. The exclusive features in LimeWire PRO were also unlocked, and all security features installed by Lime Wire LLC were removed.[15][16]

Forks and alternatives

A number of forks from LimeWire have appeared, with the goal of giving users more freedom, or objecting to decisions made by LimeWire LLC they disagreed with.

FrostWire

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: FrostWire

FrostWire was started in September 2004 by members of the LimeWire open source community, after LimeWire's distributor considered adding "blocking" code, in response to RIAA pressure and the threat of legal action, in light of the U.S. Supreme Court's decision in MGM Studios, Inc. v. Grokster, Ltd.. When eventually activated, the code could block its users from sharing licensed files. This code was recently changed when lawsuits had been filed against LimeWire for P2P downloading. It had blocked all their users and redirected them to FrostWire.[citation needed] FrostWire has since completely moved to the BitTorrent protocol from Gnutella (LimeWire's file sharing network).

LimeWire Pirate Edition

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: LimeWire Pirate Edition

In November 2010, as a response to the legal challenges regarding LimeWire, an anonymous individual by the handle of Meta Pirate released a modified version of LimeWire Pro, which was entitled LimeWire Pirate Edition.[17][18] It came without the Ask.com toolbar, advertising, spyware, and backdoors, as well as all dependencies on LimeWire LLC servers.[19]

In response to allegations that a current or former member of Lime Wire LLC staff wrote and released the software, the company has stated that: LimeWire is not behind these efforts. LimeWire does not authorize them. LimeWire is complying with the Court’s October 26, 2010 injunction."[17]

The LimeWire team, after being accused by the RIAA of being complicit in the development of LimeWire Pirate Edition,[20] swiftly acted to shut down the LimeWire Pirate Edition website. A court order was issued to close down the website, and, to remain anonymous, Meta Pirate, the developer of LimeWire PE, did not contest the order.[21]

WireShare

According to its SourceForge website, WireShare is the newest fork of the original LimeWire open source project (a successor of LPE: LimeWire Pirate Edition, which name was dropped for legal reasons). The software was developed to help keep the Gnutella network alive and to maintain a good faith continuation of the original project (without adware or spyware).[22][23]

Criticism

On February 15, 2010, LimeWire reversed its previous anti-bundling stance and announced the inclusion of an Ask.com-powered browser toolbar that users had to explicitly opt-out of to prevent installation.[24] The toolbar sends web and bittorrent searches to Ask.com, and LimeWire searches to an instance of LimeWire on the user's machine.

In LimeWire versions before 5.0, users could accidentally configure the software to allow access to any file on their computer, including documents with personal information. Recent versions of LimeWire do not allow unintentional sharing of documents or applications. In 2005, the US Federal Trade Commission issued a consumer warning regarding the dangers of using peer-to-peer file sharing networks, stating that using such networks can lead to identity theft and lawsuits.[25] On May 5, 2009, a P2P industry spokesman represented Lime Wire and others at a U.S. House of Representatives legislative hearing on H.R. 1319, "The Informed P2P User Act."[26]

One investigation showed that of 123 randomly selected downloaded files, 37 contained malware – about 30%.[27] In mid-2008, a Macintosh trojan exploiting a vulnerability involving Apple Remote Desktop was distributed via LimeWire affecting users of Mac OS X Tiger and Leopard.[28] The ability to distribute such malware and viruses has also been reduced in versions of LimeWire 5.0 and greater, with the program defaulting to not share or search for executable files.

Prior to April 2004, the free version of LimeWire was distributed with a bundled program called LimeShop (a variant of TopMoxie), which was spyware. Among other things, LimeShop monitored online purchases in order to redirect sales commissions to Lime Wire LLC. Uninstallation of LimeWire would not remove LimeShop. With the removal of all bundled software in LimeWire 3.9.4 (released on April 20, 2004), these objections were addressed.[29] LimeWire currently has a facility that allows its server to contact a running LimeWire client and gather various information.[30]

An identity theft scheme involving LimeWire was discovered in Denver in 2006.[31] On September 7, 2007, Gregory Thomas Kopiloff of Seattle was arrested in what the U.S. Justice Department described as its first case against someone accused of using file sharing computer programs to commit identity theft. According to federal prosecutors, Kopiloff used LimeWire to search other people's computers for inadvertently shared financial information and then used it to obtain credit cards for an online shopping spree.[32]

LimeWire automatically receives a cryptographically signed file, called simpp.xml, containing an IP block list. Blocking certain IPs has become commonplace and even considered essential in P2P filesharing.[citation needed]

Injunction

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Arista Records LLC v. Lime Group LLC

According to a June 2005 report in The New York Times, Lime Wire LLC was considering ceasing its distribution of LimeWire because the outcome of MGM v. Grokster "handed a tool to judges that they can declare inducement whenever they want to."[33]

On May 12, 2010, Judge Kimba Wood of the United States District Court for the Southern District of New York ruled in Arista Records LLC v. Lime Group LLC that LimeWire and its creator, Mark Gorton, had committed copyright infringement, engaged in unfair competition, and induced others to commit copyright infringement.[34][35] On October 26, 2010, LimeWire was ordered to disable the "searching, downloading, uploading, file trading and/or file distribution functionality" after losing a court battle with the RIAA over claims of copyright infringement. The RIAA also announced intentions to pursue legal action over the damages caused by the program in January to compensate the affected record labels.[36][37] In retaliation, the RIAA's website was taken offline on October 29 via denial-of-service attacks executed by members of Operation Payback and Anonymous.[38]

In response to the ruling, a company spokesperson said that the company is not shutting down, but will use its "best efforts" to cease distributing and supporting P2P software.[39]

In early 2011, the RIAA announced their intention to sue LimeWire, pursuing a statutory damages theory that claimed up to $72 trillion in damages[40] – a sum greater than the current GDP of the entire global economy. There are currently around 11,000 songs on LimeWire that have been tagged as copyright-infringed, and the RIAA estimates that each one has been downloaded thousands of times, the penalties accruing to the above sum.[41][42]

A trial to decide on the eventual amount of damages owed by Limewire to thirteen record labels, including Warner Music Group and Sony Music, all of which are represented by the RIAA, started early in May and went on until on May 13, 2011, when Gorton agreed to pay the 13 record companies $105 million in an out-of-court settlement.

Mitch Bainwol, chairman of the RIAA, referred to the "resolution of the case [as] another milestone in the continuing evolution of online music to a legitimate marketplace that appropriately rewards creators."[43]

In popular culture

See also

Similar court rulings

References

  1. ↑ https://web.archive.org/web/20150206024529/http://www.limewire.com/
  2. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ 8.0 8.1 Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ Lime Wire PRO.
  12. ↑ Lime Wire » Download LimeWire.
  13. ↑ "FrostWire Beta Released", from Slyck.com.
  14. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ Andrew Lyle. LimeWire resurrected by Secret Dev Team. Neowin.net. Retrieved November 10, 2010. (archive)
  16. ↑ enigmax. Torrentfreak %28Torrentfreak%29 LimeWire Resurrected By Secret Dev Team. TorrentFreak. Retrieved November 10, 2010. (archive)
  17. ↑ 17.0 17.1 Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ http://sourceforge.net/projects/wireshare/
  23. ↑ http://www.gnutellaforums.com/getting-started-using-limewire-wireshare/102701-wireshare-formerly-entitled-limewire-pirate-edition.html
  24. ↑ Limewire Blog Archived August 12, 2011 at the Wayback Machine
  25. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  26. ↑ http://dcia.info/documents/testimony/5-5%20DCIA%20WrittenTestimony.pdf
  27. ↑ PC Pro Magazine, September 2008 issue, p. 109.
  28. ↑ Firms discover Trojan horse targeted at Mac OS X.
  29. ↑ Lime Wire » Features History.
  30. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  31. ↑ Police: File sharing key to ID theft scheme By Howard Pankratz. Denver Post, October 27, 2006.
  32. ↑ U.S. arrest puts spotlight on file-sharing risk.
  33. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  35. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  36. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  37. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  38. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  39. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  40. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  41. ↑ Purewal, Sarah Jacobsson. "RIAA Thinks LimeWire Owes $75 Trillion in Damages", PCWorld.com, March 26, 2011, accessed April 9, 2011.
  42. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  43. ↑ Lua error in package.lua at line 80: module 'strict' not found.

Sources

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.

External links


Retrieved from "https://infogalactic.com/w/index.php?title=LimeWire&oldid=11609"