Quote:
as far as I know this problem occurs not just with the 2.44 core, but also with the new 2.6 core of the client, so this has nothing to do with using kazaa lite. plus, as far as I understand, this is rather a problem with the central supernodes that bind all small supernodes together than with the client. seems as if Sharman disabled their central supernodes servers which is the reason for the whole fasttrack falling apart in small parts.
Those 90.000 supernodes are part of the overall network and do not SPECIFICALLY contain fakes (of course there are some, as usual but not all files are fakes). If you block them in your firewall, you'll miss them later when fasttrack normalises itself.
P.S. The reason for Sharman's messing around with their central supernode servers is unknown. However, I'm pretty sure this has nothing to do with kazaa lite
this was posted by WRfan in the post below...