Despite what the ShareAza devs may think, there at least appears to be a large ShareAza population that uses the Gnutella (G1) network. Eventually ShareAza users may find they begin to struggle to connect to G1 due to using out-dated technology. Perhaps time to upgrade ShareAza's gnutella network technological capabilities?

ShareAza's old technology also causes unnecessary overhead and inefficient & costly communications (connections, searches, downloads, etc.) Might I suggest updates to ShareAza's gnutella abilities are well over-due.

I think you need to look at how the presently surviving G1 clients are advancing and for that matter, the restrictions they have been starting to use for connecting to 'older' clients. The ones still being developed: GTK-Gnutella and WireShare, and a few LW clones are still advancing slowly. Phex is still on extended vacation it seems (we hope that's all it is.)

The impression is the ShareAza Devs have a very low opinion of the G1 (Gnutella) network and don't particularly care. Is that so?
Do you care about your ShareAza user community and their obvious desires to use G1?

I make this post from an observational point of view.

A few snaps joined:



This does not happen with some of the newer G1 programs (the ShareAza connection flood.) ShareAza's connection options reduced somewhat noticeably (a fraction) to reduce redundant communications that slow the entire network down.
And far less GWC's available now. Time to find newer techniques rather than centralised sources.
Time for the flintstones to learn how to cyberspace?

Please don't let ShareAza fall short, please make changes to ShareAza so it's accepted as a more up-to-date G1 program.