Larry Nieves wrote: > Having said that, I have three questions: > > 1.- When will GTKG reach version 1.0? If this has beed discussed before, > please point me in the right direction and I will go and read that > discussion.
The idea that 1.0 is reserved for a feature-complete release. It's a rather idealistic approach. Releases are not frequent and are made out of boredom. If there's a release, people should really update and bug their package distributions, even if the version number seems to imply just minor changes. The changes are always significant albeit most of that happens under the hood and is invisible if you're just looking for changes in the GUI. > 2.- If GTKG is not publishing data to the DHT how are we supposed to > download from the provided magnet: link? I wondered myself. Maybe Raphael has a modified version of gtk-gnutella that already supports publishing. Otherwise, if nobody using LimeWire or FrostWire shares the file, it won't be found through the DHT for now. > 3.- This is probably related to the previous question: How long a time > would it be considered wise in order to label a magnet: download as > failed completely? I ask this because I'm trying to download the tarball > following the provided magnet: link (just to try the magnet: > functionality) and after more than one hour, there are still no sources. > I'm currently connected to 28 Ultranodes, 2 of which are GTKG (although > one of these is running 0.96.4). Just to see the DHT feature in action: Bitzi provides sourceless magnets. If you enabled the DHT, look at http://bitzi.com/ for speeches by Martin Luther King as these should be shared by many DHT-publishing peers, one would be enough. Likewise most other popular files should work as well. Shameless plug: See contrib/bitzify in the SVN repository for submitting metadata of your shared files to Bitzi. Bitcollider works, too, of course. The DHT feature is rather a preview in the current release. There are no GUI controls to inspect the DHT status or configure it. You might want to set dht_debug or dht_lookup_debug to some value above 1-20 to have at least some information on the standard error output respectively your log file. There's diagnostic output showing when DHT lookups are performed, whether they succeeded or failed etc. gtk-gnutella tries one DHT lookup per hour for each orphaned (sourceless) download. I believe a DHT lookup finishes in about a minute. -- Christian ------------------------------------------------------------------------------ _______________________________________________ gtk-gnutella-devel mailing list gtk-gnutella-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
