WinMX

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
WinMX
Wmxlogo.jpg
Screenshot
Winmxscreenshot.JPG
Developer(s)Kevin Hearn[1]
Stable release
3.53 / July 2, 2004 (2004-07-02)
Preview release
3.54
Operating systemMicrosoft Windows
PlatformWindows XP/Vista/7/8/10
TypeFile sharing
LicenseFreeware
WebsiteWinmx.com (archived version, currently redirects to Tixati)

WinMX (Windows Music Exchange)[2] is a freeware peer-to-peer file sharing program authored by Kevin Hearn[1] and the team at Frontcode Technologies in 2000.[3] According to one study,[4] it was the number one source for online music in 2005 with an estimated 2.1 million users. Frontcode itself abandoned development of WinMX in September 2005, but developers brought the service back online within a few days by releasing patches. WinMX continues to be used by a community of enthusiasts.[5]

In 2009, Hearn released Tixati, an ad-free freeware p2p file sharing program based on the BitTorrent protocol, enhanced with a channels function where users can chat, share lists of web and media links and stream audio and video media with all communications being encrypted.[6][7][8] More recently, Hearn released Fopnu, a client and network with some similarities to WinMX.

Beginnings[edit]

WinMX began its life as an OpenNAP client capable of connecting to several servers simultaneously, although Frontcode later created a proprietary protocol, termed WinMX Peer Network Protocol (WPNP), which was used starting with WinMX 2 in May 2001. Frontcode had operated several cache servers to aid WPNP network operation.

Downloads can be very fast for popular songs since the user can run a "multi-point download" that simultaneously downloads the same file in small pieces from several users. The WinMX program houses a few built-in features such as bandwidth monitoring, short messaging, and hosting chatrooms and functions as an OpenNap client. Users could negotiate an exchange of their files with the help of the short messaging system or chat. After the transfers start, each has the option of selecting bandwidth for the other to make sure both transfers end more or less at the same time. There is an upper limit to the size of files that can be shared (2GB). This design decision was to maintain Windows98 support. The program runs on Windows XP, Vista, Windows 7 and Windows 10 Operating systems as long as the relevant Microsoft C++ run time libraries are present.

Function[edit]

To get started, users connect to the WinMX Peer Network (WPN) either as a primary or secondary user. A majority of the functions on the WPN are available to both users, but primary users need to spend more bandwidth, tend to have better connections, and have the ability to host chat rooms. Secondary users use very little idle bandwidth, but their prolonged connection to the network is not always stable.

Sharing files in WinMX[edit]

WinMX users can share nearly every type of file using the network. The most common file types such as audio, video, images, and archive files are available by default, and all others could be configured in the program's settings. WinMX has a file-size restriction limiting shared files to 2GB in size. A user can also only share 5,000 visible files for a Primary connection (unknown if other files would be shared but not listed), and 3,000 files (maximum sent to the primary) for a Secondary connection. These limitations do not apply on OpenNap servers.

Searching for files[edit]

Users can search for almost any file in WinMX. When a user sends out a search, the search is spread throughout the network. If a file is found, the hash of the file along with IP address and Primary node details of the user with the file is sent to the user who made the search. Searches can also be made with hashes instead of words and numbers.

Chatting[edit]

WinMX allows a person to host chatrooms with its built-in Chat function. There are some rooms reserved for chat, some for trading files, and some which allow both. At its height WinMX typically had around 1,500 to 2,000 chatrooms at any given time in a multitude of languages. WinMX also allows its users to message each other using its Private Message function regardless of whether or not they were in the same chat room or are downloading from/uploading to each other. However, settings allow any user to block messages from users if they choose. It is also possible to host chatrooms in languages other than English, such as Japanese, German, French and Italian.

OpenNap[edit]

WinMX started out as a Peer-to-Peer program that connected to OpenNap servers. It can still connect to many OpenNap servers. These servers enable users to connect to a wider userbase and also receive many more search results. Two advantages of running OpenNap is the ability to have a permanent list of friends called a hotlist and the ability to display an unlimited number of files for sharing.

Translations[edit]

WinMX is natively English, but language files can be installed to translate menus into the following languages: Chinese, Dutch, Finnish, French, German, Greek, Hungarian, Italian, Japanese, Norwegian, Polish, Portuguese, Russian, Sardinian, Spanish and Swedish. A fair number of the chat rooms are in German, Dutch or Italian.

In 2002, the Recording Industry Association of Japan releases a report finding 84% of Japanese who had used file sharing software reported using WinMX, mainly to share J-pop mp3's.[9] WinMX continued to be the main file sharing client in Japan until it was overtaken by Winny and Limewire in 2007.[9] Even as late as 2013, Palo Alto Networks was finding that WinMX was the 6th most popular network in Japan.[10]

Closure of Frontcode[edit]

On September 13, 2005, Frontcode Technologies received a cease and desist letter from the RIAA demanding that they either implement filters to make it impossible for users to download copyrighted material from WinMX, or shut down. On September 21, 2005, the WinMX homepage went offline.

Resurrection[edit]

By September 23, 2005, users were able to download two unofficial patches for WinMX from two unrelated websites. These patches worked by modifying the DNS lookup WinMX uses to find peer caches.[11] When WinMX tries to find the Frontcode peer caches (central servers essential for the operation of WinMX), it is instead directed to look up one of the new peer caches set up by the WinMX communities.

In 2008 a new patch was released to coincide with the third anniversary of the two previous patches' release date.[12] Known as the "WinMX Community Patch", it was created through the joint effort of an independent, third-party programmer and the cooperative input and testing from the two communities. Supported and available for download by both groups, it is intended to replace the previous patches being used, allowing all users to once again connect to a single set of peer caches, unifying all users for the first time since the official closure of WinMX in 2005.

Network attacks[edit]

Commencing in May 2011 the WinMX network had been under protocol level attack from a disgruntled community developer (program hacker) who disagreed with those operating the network support infrastructure (user support forums & peer cache operators). As a result of those attacks the WPNP network searches would return random query results (alongside relevant results) that were unrelated to the specific term searched for, and also users were unable to receive a full chat room list.[13] A web based WinMX Chat Room List[14] was set up for users to retrieve a full room list, and also offered the ability to manually add chat rooms to the web list. In addition to offering a live list of chat rooms, it also offered a one click solution for joining chat rooms in WinMX via the web page itself with the WinMX Link Handler.[14] As mentioned above, the protocol level attacks have ceased and the network has been operating normally albeit with a reduction in network users; it's currently too early to assess the percentage of "lost" users but it most certainly exceeds several thousand and may act as a warning for other P2P networks that have protocol weaknesses that can be exploited.

Replacement clients[edit]

An initial project called WinPY attempted to make a replacement open source WinMX client. The WinPY project[15] was the most successful replacement client project as a preview alpha version with limited basic functionality was released; however, it quickly stalled due to lack of interest. There have also been several attempts to start new projects to create replacement clients however most have stalled before releasing anything fully completed. One project announced on a major WinMX community site was initially scheduled to be released in November 2012, however there were many published delays due to lack of skilled programming support. The project was finally released to public testers as a beta version on September 22, 2013 and under a new name (OurMx) and further releases will continue to be made prior to a formal client release. Historical information regarding the OurMX client progress can be viewed by following the link below.[16]

Third-party programs[edit]

In addition to the program and patches, developers and WinMX users created third party programs to either enhance the chat room function or to control uploading by other peers.

Chat[edit]

Most of the software was made by third-party developers for use in the WinMX chat rooms. They include bots, servers to host rooms, and plugins. Bots were used in the chat rooms to either make it more lively, introduce games, or to moderate users, maintain lists of the files a user in a chat room has, and more. Other plugins performed automatic functions including displaying music files currently playing on the user's computer and aid in posting colored ASCII pictures in rooms.

Third party chat servers were used primarily to host chat rooms on the network. This is because of the improved administration systems in third party servers as well as the ability to host a chat room without having to use the winmx client. Some Third party chat clients also contained useful shortcuts or menus to make administrating a channel easier. For normal users, chat clients or the WinMX client itself could be used to view rooms independently of the server. Web listings of the chat room were also available.

Upload managers[edit]

Upload managers (MxMonitor and Leechhammer) can be used to control the upload rate of peers and can block certain kinds of peers from downloading, including those who do not share any files.

See also[edit]

References[edit]

  1. ^ a b "Don't Call Them Napster - June 25, 2001". archive.fortune.com.
  2. ^ "COMPUTACIÓN: Compartiendo información - Proceso". 9 July 2004.
  3. ^ "WinMX - The BEST way to share your media". www.winmx.com. Archived from the original on 6 December 2000.
  4. ^ ""iTunes more Popular than most P2P services." DMN Newswire".
  5. ^ "WinMX World :: Home". www.winmxworld.com.
  6. ^ "Tixati". Tixati.com.
  7. ^ "Decentralized Sharing Channels". Tixati.com.
  8. ^ "Streaming". Tixati.com.
  9. ^ a b https://www.riaj.or.jp/f/pdf/report/file_exc/file_exchange.pdf
  10. ^ http://researchcenter.paloaltonetworks.com/app-usage-risk-report-visualization/#sthash.dLNpouME.dpbs
  11. ^ Mennecke, Thomas (September 23, 2005). "Slyck News - Resurrecting WinMX". www.slyck.com. Retrieved September 23, 2005.
  12. ^ Gonzalez, Jorge (September 20, 2008). "Announcement of the WinMX Community Patch". Archived from the original on September 21, 2008. Retrieved September 26, 2008.
  13. ^ "WinMX World :: WPN Attack Information". www.winmxworld.com.
  14. ^ a b "WinMX Unlimited - WinMX Chat Room List". www.winmxunlimited.net.
  15. ^ "WinPy". SourceForge.
  16. ^ "WinMX World :: WPN Compatible Client Developement Preview". www.winmxworld.com.

External links[edit]