how to control and stop dangerous client versions?
 

how to control and stop dangerous client versions?

Started by gwyn666, 15 June, 2004, 19:39:12

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

gwyn666

Is it possible to control with a bot (or a script) the client version of the people entering an hub and allow to stay olny users with the versions i have chosen (autokicking on connect people using other versions)?
If it possible...where can i find the code to use?

(the hubsoft version is ptokax 0.330 15.25 )

tnx

bastya_elvtars

Many scripts know this, altho i dont see the sense in it exactly... What would be the useful in the whole thing?
Everything could have been anything else and it would have just as much meaning.

gwyn666

#2
my friends want to stop in their hub the acces of these clients:

ofzDC++
Reverse Connect
DC:PRO
multidownload clients

and flooder programs... :)

bastya_elvtars

for flooders i recommend deflood - //www.plop.nl

for kicking certain clints dc++k cdm is better on this than a script

----------------------damn my 100th post :D
Everything could have been anything else and it would have just as much meaning.

gwyn666


tezlo

why would anyone want to block clients that support multisource download?

bastya_elvtars

#6
Multisource is a little child yet, and it causes d/l s to corrupt sometimes. In AVI movies this does not matter, but in ISOs - it makes them unusable. The solution is TTH, but many peeps (eg me) refuse to use TTH based dc++, because they eat the shit out of the machine, especially when uploading a lot,  so multisource is eroneous yet - !me hopes that it will change...
Everything could have been anything else and it would have just as much meaning.

VidFamne

Isn't TTH or some sort of hashing a basic condition for a
successful multisource downloads?

SMF spam blocked by CleanTalk