Author Topic: Network Status Information - Important - Please Read (Read 9702 times)

Forested665 · « **Reply #20 on:** May 26, 2009, 07:59:19 pm »

if we do this and emphasize the blocklist in the tutorial.
When googling winmxworld.com the second result is this https://www.winmxworld.com/tutorials/winmx_fix.html

the other day i got the third link and it was a thing on Peerguardian

MinersLantern · « **Reply #21 on:** May 28, 2009, 07:59:10 am »

This is getting ridiculous.
I've been doing my normal searches, and queing like I always have all damn day.
I'm in queue with a grand total of 2 people. Normally, thats more like 25.
Searches still work normally, the trouble is getting and esp remaining in queue with anyone.
If Sabre is the cause, block his little ass already.
I'm fairly certain the planet will survive.
Didn't kms original patch include a block to non-patched users at one point in time?
Perhaps that should be added back in as well.

White Stripes · « **Reply #22 on:** May 28, 2009, 12:05:57 pm »

well.. at least i know im not the only one out there that has the 'cant download jack' problem....

a progress report on things would be nice..... seemed everyone agreed on what to do then..... nothing else was said...

Lagerlout666 · « **Reply #23 on:** May 28, 2009, 12:33:40 pm »

I was writing up a page and im affraid life got a grab of me and had to get some life commitments out the way. Im finishing the page today and i assume we will have him blocked once i complete. Apologies.

Forested665 · « **Reply #24 on:** May 28, 2009, 05:35:46 pm »

idk about kms patch blocking. but i remember something about it putting ads in the search results for winmxgroup

GhostShip · « **Reply #25 on:** May 28, 2009, 07:42:49 pm »

What you may have forgotten is why Burn, at that time pie had a host file issue with one active peer cache server and some dead entries and that had failed at least once leaving us to be critically concerned about those users on the host file solution, nothing was being done to add more peer caches despite us calling for urgent action so KM used the single slot we had in the patch (one we where expiring and had notified Unique and sabre to stop using) and redirected folks to a pretend mx network that gave out the winmxgroup addy for any searches or room listing requests, this had the desired result and many folks updated to a superior connection method once they understood why the message was there, and many folks where dealt with in person in a specially set up room that was staffed by many of the folks here for days on end.
By undertaking this action it ensured sabre and co got their act together to release a new host file as we asked them to do beforehand, it was well documented on vladds site as to the amount of times we asked sabre and co to add more peer caches to the host file, the carrot did not seem to work so the stick was employed.

So contrary to old stories and myths no ad-flooding of the live network was undertaken except on one single occasion when the folks in the pie chat room asked KM to demonstrate the technique for them which he did, that is the only time such a technique was used in the wild and it was with both our and pies knowledge and permission.

Forested665 · « **Reply #26 on:** May 28, 2009, 10:25:51 pm »

I wasnt concerned with why. but it is nice to know as there are a few details there I hadnt heard before.
And leads me to believe that the issue was a security breach?

GhostShip · « **Reply #27 on:** May 28, 2009, 11:11:33 pm »

I,m always ready to fill in any blanks folks may have in squaring what happened and why, but I suspect most users dont care too much about the old days of fighting and community splitting rhetoric, what we have proposed will not actively impact on any users choice of how they join the network but we are hoping it will demonstrate action is needed to secure as much of the network and the bandwith folks share as possible, for genuine users rather than media defender and their ilk.

I am always contactable here and in the chat room for folks wishing to know further details on our efforts to secure their privacy, we are hoping the community can look above any one team or group and pull together to close the door that has been held open to our attackers for so long by one misguided individual, democracy is not something many people take a lot of notice of but to us all users are valued and worth going the extra dollar for, no users=no community.

Btw I dont understand what you mean by a security breach but feel free to explain as long as it doesnt involve area 51

Forested665 · « **Reply #28 on:** May 29, 2009, 01:09:30 am »

idk how to word this to keep area 51 out of it.
but... like... what was the purpose of that demonstration was it to prove that there was a breach/hole that could be taken advantage of? , or was it something more childish like KM just wanting to show off?

Savage Blades · « **Reply #29 on:** May 29, 2009, 01:29:52 am »

Time to stop pussy footing around...
Many Pie 3.6 users simply don't know the difference between the patches..
they get fed up with the fakes in searches and rate mx because of it..
(Going back to the days where pie & wmw were divided)
Maybe even to point where they get fed up and leave the network taking their files with them.
Pie 3.6 is herpes on the winmx network..
Sabre has been pleaded with.. to no avail.
As of today there are still more winmx help rooms promoting 3.6 than Community Patch
Therefore as I educate and convert 3.6 users... current CP1.0 users with a connection glitch go looking for help and stumble on a Pie room..odds say they will
So the vicious circle continues..
So it's not personal... about this group, that group..
It is about 'what is best for winmx as a whole ?'
Now. that said..
What will happen when certain parties who are trying 24/7 to flood the network can no longer connect ?
Their current methods are tolerable.. we live with it and deal with it...
Will they look for new ways to harm the network after their current method fails ?

Lagerlout666 · « **Reply #30 on:** May 29, 2009, 09:36:20 am »

Possibly savage, and we do as we always do. Adapt. What about these people who run rooms. Maybe we should organise a Motd change your patch day. So alot of rooms in the chat list all have the same MOTD saying update from 3.6 patch. A little gimmick that could work???

And for you peeps to have a look over

https://www.winmxworld.com/tutorials/segregation.html

Sorry it took a little longer than planned. But please take a look at what im saying and if you have any questions please dont hesitate to contact me.

White Stripes · « **Reply #31 on:** May 29, 2009, 12:31:48 pm »

from your page;

Quote

This means that most of them will be full and sabers aches will have to work harder to find emptier primaries.

a bit of a typo.... ....just lettin ya know....

wonderer · « **Reply #32 on:** May 29, 2009, 01:19:50 pm »

Let me add another typo, his name is Sabre

Lagerlout666 · « **Reply #33 on:** May 29, 2009, 02:41:48 pm »

Lol fast as ever guys. An it was a work on progress. Ive amended said issues. And got a few more facts to add to it.

White Stripes · « **Reply #34 on:** May 29, 2009, 03:53:04 pm »

Quote

as you can see from the picture's thier are no primary to primary blocking

two more... lol.. ("picture's" is grammatical... no need for the apostrophy)

Lagerlout666 · « **Reply #35 on:** May 29, 2009, 04:25:55 pm »

~~birdman~~ · « **Reply #36 on:** May 29, 2009, 04:27:16 pm »

Maybe instead of the wording DLL on the segregation page replace it with "comunity patch" as maybe the word dll has a bit of stigma for people on the host file fix, just a thought and also maybe more info about the current attack and its effects so people can see why theres the need to block sabres caches

wonderer · « **Reply #37 on:** May 29, 2009, 04:36:58 pm »

Dll or Community Patch, as long as it is clear it should state community patch in the WinMx messagebar to be safely patched.

Forested665 · « **Reply #38 on:** May 29, 2009, 07:37:48 pm »

I think this is most disturbing

wonderer · « **Reply #39 on:** May 29, 2009, 08:48:22 pm »

That post is almost three years old and at least you can say it is outdated