Foxy

[wiggindesigns]

From the devs, can we have some ideas on how to filter out the foxy users? Since I doubt there will be a collaboration anytime soon it would be nice to have a way to filter them out without blocking ALL TW/HK users.

Shareaza uses RAZA right? Don't all p2p programs have this type of code that could be used to filter out the foxy spam?


Not sure, as I don't know the inner-workings of shareaza. But it would be nice to hear from the devs as to viable options, and the likelihood of it working.

[raspopov]

Add content security rule for string "Foxy".

[wiggindesigns]

Would that actually block the users of the foxy program tho?

[scman14]

go to help and support.. look for block foxy from plesko
it tells you more
i hope this helps

scman14

[wiggindesigns]

I know the IP part, i created the whole IP list. Im looking for an alternative that doesnt require blocking all of TW/HK because some of them also use shareaza and limewire etc.

As for the user-agent filter, i'd prefer to see the foxy user-agent so i know "foxy" will actually work\

After some research, there have been reports of "spiders" with the UA of "Foxy/1" which originate primarily from HK/TW... Now if Shareaza just implemented it as a default UA

[cyko_01]

[loopyloo]

After adding "foxy" and "mxie" to the user agent filter foxy and mxie clients no longer upload from me. But it doesn't stop search results from foxy/mxie clients. I've taken to banning any foxy client I get results from.

[plesk90]

See this topic viewtopic.php?f=3&t=178&start=0

[old_death]

In any case it would be better to crack the foxy authentification, wouldn't it? If anyone has a good relation to a hacker community... feel free to post the challenge there.

IMHO, G2 should become totally free again...

[ocexyz]

+1
challenge is challenge....

[lostcowboy]

Maybe if people send email to the Foxy programmers it will help solve the problem. Here is the email address for foxy support. [url]support@myfoxy.net[/url]

[raspopov]

Send it then.

[loopyloo]

Blocking China, Taiwan and Hong Kong from connecting to shareaza with an IP filter seems to stop the problem of Shareaza's host catch filling with foxy hosts. As you would expect I guess. Shareaza was becoming unusable so I took the step.

Edit: Shareaza now maintains a stable G2 connection. Beforehand it was losing G2 connectivity every 30 min or so.