----- Original Message -----
From: "Ryan Perdue" <ryanrain@xxxxxxxxxxx>
To: <winmxfortheblind@xxxxxxxxxxxxxxx>
Sent: Wednesday, September 21, 2005 3:35 PM
Subject: [winmxfortheblind] WinMX PNP Network Mysteriously Ends Operations
WinMX PNP Network Mysteriously Ends Operations September 21, 2005 Thomas Mennecke
WinMX began its time as a simple OpenNap client in a time when Napster and
Scour ruled the P2P scene. When Napster and Scour were banished from the
Internet,
WinMX's importance took on a new burden of importance. It reinvented itself
from a mere OpenNap client to become one of the premier P2P networks of its
day.
During its height, WinMX, developed by FrontCode Technologies, eclipsed the
Napster P2P network in not only resourcefulness, but also in population.
During
mid-2002, its population had reached over 1.5 million simultaneous users.
With an active community, plenty of independent user forums and steady
development
it appeared there was nothing that could stop this network.
Then something mysterious happened. From July 2003 to July 2004, there were
no updates to WinMX - nothing to improve the network architecture, the
dreaded
queues or any other attributes. Then in July 2004 after nearly a year of
frustration, FrontCode released what many perceived as a mere "filler"
version.
Version 3.53 did little more than feature "a major upgrade of the chat
component and other minor improvements."
That would be the last anyone would hear from WinMX ever again. Slyck
maintained communications with FrontCode president Kevin Hearn, who stated
that work
was still being continued on the mystical version 4.0. During the early part
of the summer, Mr. Hearn told Slyck.com that something might be available
towards the end of the 2005 summer.
However, another plot twist appears to have mixed things up once again. On
September 13, 2005, WinMX was the recipient of a letter (along with 6 other
P2P
firms) from the RIAA. The letter demanded the receiving developers they
cease infringing operations immediately, and offered to "discuss
pre-litigation
resolution of these claims."
Like Alberto Treves' decision to release the source of Ares Galaxy, or Sam Yagan's decision to join the DCIA, every move a P2P developer makes is immediately questioned to be in direct response to the RIAA's letter campaign. Such is the case for FrontCode Technologies. Or should we say WinMX Technology Associates?
Currently, the WinMX.com homepage, the FrontCode.com homepage, the WinMX PNP
Network and all of its host caches are down. It is impossible to connect to
the network, and those remaining online will only stay online as long as
their host supernodes do. But is this the end of WinMX?
Perhaps not. Interestingly enough, if one conducts a DNS whois for "WinMX.com", the result directs owner ship to a "WinMX Technology Associates" - not FrontCode Technologies as it has in the past. Even more interesting is the geographical relocation from Toronto, Canada to Port Villa, Vanuatu. Many will remember that Sharman Networks pulled a similar stunt to avoid prosecution in the Netherlands and to capitalize on "tax efficiencies."
FrontCode.com is still registered in Canada. Kevin Hearn, who is usually
readily available for comment with Slyck.com, has not responded to inquiries
for
several weeks.
Before anyone clamors the end of the WinMX PNP network, time needs to be given to allow for this development to unfold.
====================================================================<<< Whatever you Wanadoo, click below: http://ads.smartgroups.com/adclick/CID=000000b7c79a99a500000000 ====================================================================>>> -- If you want to share pictures, use the calendar, or start a vote visit http://www.smartgroups.com/groups/winmxfortheblind
To leave the Group, email: winmxfortheblind-unsubscribe@xxxxxxxxxxxxxxx
Report abuse http://www.smartgroups.com/text/abusereport.cfm?gid%3D2265666&mid%3D2143
__________ NOD32 1.1228 (20050921) Information __________
This message was checked by NOD32 antivirus system. http://www.eset.com
** To leave the list, click on the immediately-following link:- ** [mailto:access-uk-request@xxxxxxxxxxxxx?subject=unsubscribe] ** If this link doesn't work then send a message to: ** access-uk-request@xxxxxxxxxxxxx ** and in the Subject line type ** unsubscribe ** For other list commands such as vacation mode, click on the ** immediately-following link:- ** [mailto:access-uk-request@xxxxxxxxxxxxx?subject=faq] ** or send a message, to ** access-uk-request@xxxxxxxxxxxxx with the Subject:- faq
