WinMX

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.

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.

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.

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.

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.

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]

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.

• File sharing in Japan
• OpenNap
• Perfect Dark (P2P), a Japanese successor to Share
• Share (P2P), a Japanese successor to Winny
• Utatane (P2P), a Japanese OpenNap client
• Winny, a Japanese filesharing program somewhat similar to Freenet

• WinMX World