WinMX is currently protected from NOTHING!

Have you noticed that the WinMXWorld website is down right now? Well if you haven't you should probably know what it means to you, and why they're such an irresponsible and clueless organization.

Cache Servers Have NO Blocklist?

Since every WinMX peer cache server relies on a text file hosted on the WinMXWorld website for their blocklist ip ranges to give to actual WinMX users (www.winmxworld.com/block/cache_list.txt), they are currently being fed a generic 301 "Moved Permanently" error code message. These redirect codes (301/302) and used to tell your web browser that the website or web page you are trying to visit has been moved temporarily (302) or permanently (301). As it seems the admins at WinMXWorld have no clue what they are doing, they have set a 301 code. Indicating that the website will never return. I sure hope Google has discovered this so our relevent blog posts can move up a few spots to the top of the search results for "winmx world".

 Check for yourself here: http://www.winmxgroup.com/index.php?id=cache-checker  (just click any of the "Online" spots under the blocklist column)

Because of this severe oversight of the WinMXWorld admins and their "coders". All WinMX users are currently being bombarded with fake files in their search results, as well as being completely unprotected from any of the cartel organizations connecting directly to them.

Below is an example of thousands of fake files, along with whois' of maxed out secondary users as we remember seeing from years ago when the fake files first started:

Why this shouldn't have happened:

Due to the way the cache server and the patch that they and every WinMX user is using, there are no integrity checks built in to prevent this kind of thing from happening. You would think someone would make sure that the cache servers would not replace a list of actual ip ranges with a block of html garbage... and you would think the patch would be designed to not forget all of the previous ip ranges from the REAL block list before it adds in a block of html... but I guess no one was smart enough to think of that.

When can we expect a fix? Who knows... we still haven't received a fix for these network attacks. I would say an estimate of 2015 is a good guess. But I can assure you, this group of people running WinMXWorld really has no fucking clue what they are doing, and if this doesn't convince you, I don't know what will.

One Year Later...

It has been over one year since the attacks on the WinMX network started. And look where we are... the exact same place that we were a year ago. Isn't that just pathetic?

Let's first take a moment to thank GhostShip for all his hard... ohhh wait..

Patch? What patch?

Over the course of the last twelve months WinMX World has promised a fix for these issues in the form of a patch, but what exactly happened to this so called quick fix patch? Perhaps GhostShip pissed off yet another "talented" developer with his dictator like attitude and lack of intelligence in how to actually code a working program?

Well folks, I'm sad to say that GhostShip confirmed on the WinMX World forum himself that they have abandoned the patch method of fixing this minor issue with the network. It seems Richy's version of the patch was not good enough for GhostShip to slap his name on and call it his own, so he chose to let us suffer even longer in this mess.

The Replacement Client (And Why It Already Sucks):

Instead of a patch, WinMX World now promises to release a replacement client. When and if this may happen is unknown, but Tiny4Eva/Ryan promised months ago that it would be released in a "few weeks". However, here we are, months later and they have nothing to show for it. The fact is people, this replacement client is not going to actually fix anything. To fix the fake search results, it simply filters search results on the client side. This may look like a "fix", but your search requests are still going to be turned into "c:", and you will receive maybe 1/10th of the amount of search results as you did before the attacks started. For a chat room list fix, they will probably host their own incomplete and outdated list of chat rooms to load into the client remotely.

So much for actually fixing the problem right?

We all see what GhostShip has done for us...

 NOTHING at all.

Who is really behind these attacks?

Has anyone stopped to realize that the only group of people that benefit from these attacks is WinMX World themselves? Think about it for a minute, KM and Splintered have not been seen for months, and yet the attacks continue? If the attacks are active, people have a reason to visit the waste land known as WinMX World, and they have a reason to look to them for help and advice. The fact is, the patch we use now has not been updated since 2008. FOUR long years we have gone without even a little update. Updates such as local peer discovery that would eliminate the need for peer caches (and remove their monopoly of the network), and updates such as adding a local search filter that would actually 'fix' the search hijacking problem.

The actual reason for the patch never being updated is the fact that they rely on a foreign coder. And because GhostShip can't actually code, and all the decent coders in the community got sick of him, he had no one to turn to.

So, think to yourselves... if WinMXWorld is the sole beneficiary to these attacks... then...

Please GhostShip, do what we all want: