leecharza?

[-|0_0|-]

I gave it a try shareaza and found it allows to disable partial downloads sharing & upload queues(checking off 'enable this queue' in uploads setting->queues->edit->capacity).
In those settings,shareaza does not upload at all,while download smoothly on G2.
I think,it's not good as G2 client but also as hybrid client,considering the whole upload bandwidth of networks...

[isus]

if you disable partial sharing, you don't share what you are downloading. you still share what's in the shared folders... it doesn't disable sharing entirely.

[cpugeniusmv]

and if there's nothing in your shared folders, and you're not sharing partials (and you're only connected to G1 and G2) then you won't be sharing anything.

but if you use shareaza to connect to ed2k, it automatically turns partial file sharing back on...same with bittorrent. and you cannot disable that.

[johoja]

I gave it a try shareaza and found it allows to disable partial downloads sharing & upload queues(checking off 'enable this queue' in uploads setting->queues->edit->capacity).
In those settings,shareaza does not upload at all,while download smoothly on G2.
I think,it's not good as G2 client but also as hybrid client,considering the whole upload bandwidth of networks...

theres an edonkey guard queue, so basically don't think tha would do anything.
bittornet uploads outside the queues so again...nothing would happen to that. You can disable sharing on G2 because its an open network and they are no standards unlike Edonkey/Bittorent.

[-|0_0|-]

in the settings I mentioned above,
leechers can suck from clients like gnucleus,limewire... and from hybrid mode shareaza which are connected to ed2k & gnutella via G1 and G2.
I still think that would hurt networks.

so,the best settings for normal users might be more upload bandwidth & queue slots to ed2k and less to G2 ,for getting credits.
If many ppl make such settings, the efficiency of shareaza's transfer methods (e.g. active queues , small chunk size) would be diminished, I think. :(

[johoja]

in the settings I mentioned above,
leechers can suck from clients like gnucleus,limewire... and from hybrid mode shareaza which are connected to ed2k & gnutella via G1 and G2.
I still think that would hurt networks.

so,the best settings for normal users might be more upload bandwidth & queue slots to ed2k and less to G2 ,for getting credits.
If many ppl make such settings, the efficiency of shareaza's transfer methods (e.g. active queues , small chunk size) would be diminished, I think. :(

Any of those clients ie) bearshare/limeweire/put your gnutella client here can be used to leech. To the best of my knowledge they do not force Sharing. The main two bearshare/limewire don't have PFS support as of yet either.

[cpugeniusmv]

in the settings I mentioned above,
leechers can suck from clients like gnucleus,limewire... and from hybrid mode shareaza which are connected to ed2k & gnutella via G1 and G2.
I still think that would hurt networks.

so,the best settings for normal users might be more upload bandwidth & queue slots to ed2k and less to G2 ,for getting credits.
If many ppl make such settings, the efficiency of shareaza's transfer methods (e.g. active queues , small chunk size) would be diminished, I think. :(

shareaza enforces sharing when connected to ed2k and bittorrent. you cannot turn it off when connected to these networks. even if you disable sharing in the options, it reenables itself when you connect to ed2k or bittorrent.

[-|0_0|-]

I know about forced sharing..ed2k guard..
but honestly,I'm still a newbie on shareaza.
then, clients enabling G2 only can not download from hybrid mode(connected to both G2 and ed2k) shareaza clients?

anyway, all upload requests from shareaza and other G1 clients were rejected in leech mode.
(connected to G1 and G2, PFS disabled , all "enable this queue" option in the upload queues properties of small,medium and large files disabled)

I'm now off such mode and am uploading files I got mainly from shareaza sources with "H" icon.