Hi, On Saturday 12 June 2004 13:29, Richard Eckart wrote: [...] > > Personally I don't like being forced to update a stable version just to > > get rid of the beep (I needed half a day to figure out its source since > > GTKG runs on a remote machine)... > > We have had several stable versions which contained serious bugs which > hurt the network. If you run a version which is known to have bugs, > there is a big chance that other servents will not let you connect, > including newer versions of gtk-gnutella. Only because you run a version > which was once released as stable, this does not mean, that it is still > a good idea to run it on the gnutella network. Users have to upgrade > from time to time and we need to nudge them to do. Ah, I see...
Hmm, GTKG obviously has a way of detecting whether a new version is available. Maybe this mechanism could be extended in a way that GTKG still beeps if the user really *should* make an update (e.g. because he is running a version which meanwhile is *known* - or at least supected - to be hurting the network) ? But of course you have other priorities, it's just an idea. Anyway, compared to other Gnutella servants (even more "colourfull" ones) GTKG simply rocks. Especially the filter stuff (which allows me to trigger automatic downloads) is the greatest invention since that of sliced bread, I guess ;-) kind regards Martin -- "Things are only impossible until they're not" LibChipcard - http://www.libchipcard.de OpenHBCI - http://www.openhbci.de ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ Gtk-gnutella-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
