|
|
Posted by DB_Story on 12/11/05 06:02
"George Hester" <hesterloli@hotmail.com> wrote in message
news:CaOkf.95297$JQ.72576@twister.nyroc.rr.com...
> "DB_Story" <DB_Story@att.net> wrote in message
> news:udKdnR_cI7njbgzeRVn-vg@comcast.com...
> > This was never part of the original version, but it would be nice IMHO
if
> > the cache servers did a Whois as part of bringing a new user onto the
> > network, and if they have the Zero Uploads Hack active, refuse to admit
> > them. I know that hack is still out there because LeechHammer still
> catches
> > and hammers a couple of them a day. I believe that hack can be applied
> > after they're on the network, but not letting them on in the first place
> > would be a nice start.
> >
> > Technically, if the client does not allow a Whois until the network
> > connection is active, connect them to a test network, run the Whois,
drop
> > them off of that and connect them to the live network. It's more than
> past
> > time to kill that hack altogether. If you don't want to share, then
don't
> > share any files.
> >
> >
>
> That function in Leechhammer is a joke. I had a user that was sharing
files
> and I was trading with them. Leechheammer ignored them for sharing 0
files.
> That was the last time I used it.
>
Two things:
1: You have to enable the zero uploads hack test in LH.
2: It has nothing to do with the files being shared. They can be sharing
the limit of 5000 files, but still have their WinMX client hacked to allow
ZERO uploads. That effectively prevents them from sharing anything despite
how many files they have listed in their share directory.
My belief is that you may not have had your LH configured as you thought it
was. You also have to tell it what action to take with people sharing 0
files.
Navigation:
[Reply to this message]
|