0 Members and 2 Guests are viewing this topic.
I'm sure there are a lot of people who like the fact that I actually do things - like restoring the network when frontcode went...history? you mean a history of always stepping in when required to do what is best for the network, no matter how costly it is to myself? or you mean the history of always fighting against those who attack the network? would you also like to mention the history of this group now calling themselves "pie"? with the "child abuse" (i believe that is the politically correct term for raping children), amongst other things - very nice history they haveincompleteness? what is missing? i mean apart from the repeated demands you have made that i give you an attack tool that can shut down the entire network in a matter of minutes...
Some of you here may know I represent a non pie site and along with you all I agree the fighting is getting a little out of hand. The reason for many of pies problems are in there own hands and I have had hundreds of posts complaining of Censorship on vladds site of the more viable winmxgroup solution which I of course support for technical reasons. As I see the allegations have been placed on this forum I feel its only fair for me to respond to them. On the 31st of may a change was made in the IP,s of two peer caches as it was noticed during a routine check of the logs that a denial of service attack had been ongoing and this was a simple pre prepared way to avoid those perpetrating the attacks, the plan originally involved rotating the peer cache addresses which would have no affect on the winmx group users but pie users would be affected so this was shelved and a single change was notified in the usual manner of previous change notices, a public posting https://forum.winmxworld.com/index.php?topic=2425.0.html This so far would have caused a mere delay in connecting and should have been the time to issue an updated host file, but lets move forward in time two weeks. Problem 2 arose for the pie team, Rocks peer cache (209) went down and all further pie traffic was diverted to Leps peer cache (82.4, this is a home connection and as can be expected it was soon overwhelmed with traffic. The release of the new winmxgroup patch was a news aricle here and has proved a major success with those using its new fake blocking features. Now we come to the cause of the renewed fighting, user who had discovered the new patch and posted on vladds site regarding how well it worked and that it connected instantly found their posts being deleted, depriving others from finding the alternative connection solution. Users going to the vladd44 rooms where also being mislead regarding the new patch development, many being told horror stories such as it was a trojan, didnt work with routers, damaged windows and many other untrue allegations. We and I speak on behalf of winmxworld and winmxgroup do not support this type of censorship or action against winmx users who only wish to connect. We are also unhappy regarding advertisements found on vladds and the mxpie site for pay winmx, we feel this is wrong and this is not the first time we have seen these advertisements there or complained. For the information of those who may be puzzled by such strange activity and why the stakes are so high regarding this matter, the pie/host file users are the sole source of access for Macrovisions flooders into the WPN,it is next to impossible to upload fake file lists to a primary winmxgroup patch user. I have very much respect for all the posters here and had not wished for this "internal" matter to spread over into the wider world of p2p, but as it has done I am quiet willing to answer any further questions on this matter to satisfy those who have concerns and wish answers.
Yes I can answer that mystery also The users who have not been able to connect using pie patch where left with non operative winmx systems and so we decided to take the initiative in helping these users back onto the network, this was done by bringing a reserve winmxgroup cache serve online on the old alternative address that was in the pie patch and direct these users to an update message thats told them their patch was in need of updating. We feel that this action is in the best interest of the users and the network, as losing users is not in the interests of ourselves or pie. Users who received the message that appeared on the channel list and on a single search result, where confused as to what was happening but at no time where they connected to the wpn, the connection was dropped after a time thought long enough for the users to read what was happening and take action. What I beleive happened in some cases is that users who entered the update server used a facility of winmx to connect via TCP to a chatroom directly and as the connection dropped at the update server their name numbers where reassigned again as they re-entered the update server again,and this was reflected in the chat room seeing a change in usernames, Of course we had tried to cover all the angles in asking people to upgrade their patches, but it seems some folks neither bother with a roomlisting or search for files and these where the only methods we had to contact those on defunct pie patches. I hope that clears up the mystery, I would like to add only one member of the pie team (Unique) asked for the information above and I readily appraised him with the same information posted here
The users who have not been able to connect using pie patch where left with non operative winmx systems and so we decided to take the initiative in helping these users back onto the network, this was done by bringing a reserve winmxgroup cache serve online on the old alternative address that was in the pie patch and direct these users to an update message thats told them their patch was in need of updating.
Keep adoring your chocalate god by all means, don't even doubt his words. He and he alone saved WinMx, that's what he beleaves, so you should all beleave.
