0 Members and 1 Guest are viewing this topic.
19:04:11 This Channel is hosted on WCS 1.8.3-Win3219:04:11 Topic: Information about why the recent attacks have taken place, and what WinMXWorld is up to, come inside for information.19:04:11 19:04:11 Welcome to the room.19:04:11 19:04:11 In this article, I am going to explain a bit about the situation on the network. You may have asked "What is the issue? What's the point of all this? How did this all begin? Why am I being involved when I am just an ordinary user?" and I will try to get it covered here:19:04:11 19:04:11 The issue started when an independent developer wanted access to some protocol information about the network to develop some third party applications on their own, without involvement with any other developers. WinMXWorld has had this information hidden from the public, and only a limited group of WinMXWorld people have had access to it.19:04:11 For WinMXWorld to release any of this information, they required the person requesting the info to join their developer team and got involved with them. There is nothing overly wrong about this, if they want to keep their protocol info closed, that is up to them, they have the right not to share it, even though I personally believe this is rather counter productive on a network like this.19:04:11 19:04:11 19:04:11 Since none of this information was released by WinMXWorld, the developer decided to gain access to this information from another source by contacting KM, an old developer with extensive understanding of the network, as he had also worked out the same information that WinMXWorld was holding back (In fact, KM provided most of this information to WinMXWorld).19:04:11 The developer explained the situation about WMW holding holding back on the info to KM. That was when KM decided to publish his own written documentation about the network in an attempt to break up WinMXWorld's strong monopoly on the network. He believed that WinMX was supposed to be an open and decentralised network with no single group being fully in charge of operating the network.19:04:11 19:04:11 However, when it came to WinMXWorld's attention that these documents had been published, they decided BLOCKLIST the user sharing these documents from the network.19:04:11 This was the point where a very immoral decision was made by WinMXWorld, as they had now proven how a single group is in fact able, and willing to blocklist individuals for the files they are sharing, which widely breaches the fundamental principle of a decentralised network.19:04:11 This blocklist was only intended to block and filter the recording industry's fake file flooders from the network, and nothing else. While WMW has been trusted to run an unbiased blocklist for a long time, the same cannot be said now. 19:04:11 19:04:11 19:04:11 19:04:11 Discussions were raised in the WMW help room about whether these actions were moral or not, but WinMXWorld did not want to remove the entries from the blocklist, no matter how much pressure they got from the users around at the time.19:04:11 The WinMXWorld admins responded by resorting to kickbans and insulting the users questioning them, in an attempt to neglect the entire situation and move on as if nothing had happened.19:04:12 WMW were repeatedly warned that if they did not do the right thing by removing the entries from the blocklist, action would be taken to force them to do this.19:04:12 19:04:12 19:04:12 Since WMW kept refusing to remove the entries, it became apparent that the only way to get the entries removed was with force. A larger userbase was needed for WinMXWorld to realise the seriousness of the network principle they had just breached.19:04:12 Some light attacks were done on the network to get attention from more users on the network, was by temporarily saturating the network's resources to lower the performance of the network to a noticable point where users would come to WinMXWorld where they could get themselves informed about what was going on.19:04:12 19:04:12 WinMXWorld kept up with their insults and kickbanned many users that dared speak up about their opinion in the matter. Not only did they kick and insult the users that they didn't know, but they also insulted many regular WMW room visitors that had been around for a long time, that probably believed that they were valued and would get listened to.19:04:12 Instead they were just told off, and the entries remained on the blocklist.19:04:12 19:04:12 After several days of pressure from many random users, and with pressure from yet another "attacker" that had surfaced (yet unknown to me) that was injecting a message into the network reading "When ghostship loses his huge ego this will stop", WMW finally decided to give in, and said that they would remove the entries.19:04:12 The attacks stopped, and WMW were given some days to get the blocklist sorted. KM also forced them to create a new forum section where the current blocklist was would be posted, and each entry on the list would be documented with a reason of why the entry was added.19:04:12 This was to make the blocklist more transparent by allowing any interested users to check the current blocklist, and questioning the validity of the entries.19:04:12 19:04:12 This looked good for a few days, but later on, WinMXWorld decided to add some new entries to the blocklist. These changes were not documented, and some incorrect entries had been posted in the forum section, or so I've been informed. The attacks continued trying to enforce the agreement that had been put in place.19:04:12 19:04:12 As of the time when writing this, the entries have been removed again, and the documentation in the forum is accurate (even though some of the entries for fake file flooders are obsolete and inaccurate).19:04:13 19:04:13 19:04:13 19:04:13 You might be interested in hearing what WMW has to say about their attempts to censor the protocol information from being published.19:04:13 19:04:13 WinMXWorld will try to defend their actions by saying they did it in an attempt to protect the network in the event the information would get into the wrong hands, claiming that this information in the hands of an attacker could bring the network down. However what they were really worried about was their monopoly, they wanted to censor this information as it could weaken their19:04:13 strong position on the network if this information was made available to the public. Also, the information needed to make an attack utility has always been widely available for anyone, and WinMXWorld has been aware of this. However the information needed to make progress and develop useful third party applications has always been hidden from the public,19:04:13 and this additional information was the info that was published by KM, and held back by WinMXWorld.19:04:13 19:04:13 19:04:13 19:04:13 In the end, I also want to add that while the discussions about the immoral blocklist entries were going on, suggestions about how the network could be decentralised even further, and a technical solution of how to distribute authority to multiple parties in a democratic and secure way was suggested.19:04:13 These suggestions were of course opposed by WinMXWorld. Overall it is very apparent that WinMXWorld only cares about their strong position, and not what is to the best for the network.19:04:13 I hope that WinMXWorld will refrain from abusing their position in the network, and that they will get some structure on the work they do, by creating some internal ethical guidelines, where they have taken their position in the network, and the basic principles of a decentralised network into consideration.19:04:13 19:04:13 We hope that this information has made you aware of what is going on, and that you understand why the attacks have taken place in order to win this important principal battle. The attacks were not done merely to cause disruption like WinMXWorld might want you to believe.19:04:13 Please spread the word, by letting your friends know, and let WinMXWorld know what you think about their actions. Stand up and defend our network now.19:04:14 19:04:14 ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^19:04:14 PLEASE SCROLL TO THE TOP TO READ THE WHOLE STORY. PLEASE SCROLL TO THE TOP TO READ THE WHOLE STORY. 19:04:14 PLEASE SCROLL TO THE TOP TO READ THE WHOLE STORY. PLEASE SCROLL TO THE TOP TO READ THE WHOLE STORY. 19:04:14 This is not intended to be a chatroom, just a room for reading the story. Feel free to stay or leave as you please.19:04:14 ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^19:04:14
they have had a few small attempts at getting past us but so far they have failed however if a list with all of their IP Addresses on it was public and kept updated then they would put a lot more effort in to disrupting the detection methods
2. the issue of winmxworlds insistence on trying to get together information on the network, now you are well aware (the most senior admins are definitely more than aware, others will have seen it mentioned and i should hope would be smart enough to have figured it out) that this information in the wrong hands is extremely harmful not only to the entire network, and to every single user on it, but also endangers every other user on the internet even if they have never heard of winmx before - now this dangerous information you have, it has been announced on several intentions you plan to release it to the public... care to try to justify this? and will you still be stubborn enough to deny a problem whilst your home connection is being hit with 400Mbit+ of attack traffic using the information you insisted on releasing ?