A new version of the proxy blocker v1.6.1 was released today. It uses a completely rewritten API (Proxy API v2). It no longer uses winmxunlimited.net for any of its functions, everything including the pre-emptive ban system and proxy checking has been moved to MXPulse. This is due to Josh working on other projects that he is more excited about, I'm still excited about security so I have taken over the proxy blocking API development.
The new API as of this message has over 200,000 Proxy servers on record just from what it scanned in the past 24 hours. It's the fastest API written so far for this usage and can support searching through millions of IP Addresses for detection.
But most importantly this version of the Proxy Blocker client is 2x faster at querying the API. The analytics discussed in the earlier part of this thread have also been adjusted positively for users.
In the old version if a proxy server was detected entering a channel the client would send a second query to an analytical API detailing the room name, IP Address and Username of the proxy user who entered. The new version doesn't perform this second query and instead tacks on the channel name on its original IP Check query. I no longer receive the usernames of people at any point even if they are using a Proxy Server to enter your channel, I only get their IP.
I found that collecting the usernames of proxies that entered your room didn't really help that much in finding where proxies came from. The only thing it provided me was insight as to why certain rooms were being attacked but that is outside of the scope of why I wanted the data, to find the websites where users gained proxies. So in the new version I removed the name sending completely.
The new version can be downloaded here: http://www.mxpulse.com/board/viewtopic.php?f=9&t=194
It does include some other new features such as a verbose mode, signed API responses for security and a key system which I may use in the future to give WinMX users precedent when accessing the API over other types of API queries. But really the main feature here is speed, the 2x faster querying has meant that in my testing it can kick and ban a proxy entering your room in under 250ms, of course your mileage may vary and the closer you are to the API (Hosted in UK) the faster it will boot proxies out.
I wanted to make this update here just so people know I am still working on it, this and all my other software is still being updated as are their associated web services