Has LimeWire program behaviour become a Rogue identity in the Gnutella environment?
 

Using LW Pro 16.6, I found that LW users were stealing all my upload slots. Phex users were being pushed out of the queue. I turned partial file sharing option off. This did make some improvement seeing more Phex users in the queue, however still Phex users were being pushed out; all open slots went to LW users, else LW users would steal all the upload bandwidth. Then often Phex users would be pushed out of their upload slot after a time. I have about 15 snapshots over a few hours which I could provide if requested to prove this happening.

Last time I saw behaviour as aggressive as this was some years ago with Morpheus & some versions of other gnutella clients.

I do not believe this is fair behaviour on the gnutella network & whether deliberately or unintentionally, this aggressive behaviour by LW has crept in.

It was already known LW searches tend to favor other LW users. It seems they wish to steal the gnutella network for themselves, at least that's the impression it gives, and leave other gnutella clients out in the cold.

So my questions are:
* Is this behaviour acceptable now for gnutella clients?
* If above answer is yes, then why doesn't Phex take a more aggressive approach at making sure their users connect more easily with LW users? (I like to use Phex for numerous reasons, one of them being that it connects to many more 'other' gnutella clients & finding files that LW doesn't seem to be able to.)
* What should be done about this?

I think, first we should test, if it isn't a bug in Phex which makes us lose the upload slots.

If it isn't a bug in Phex, the second step should be to write in the public Gnutella Development Forum, that we experienced problems when downloading from LimeWires.

There might still be a perfectly valid explanation for that.

And if it turns out that LimeWire really tries to push out Phex, I think we should team up with gtk-gnutella and (though I prefer single network clients, everyone counts) Shareaza.

BUMP!

I agree too. Unfair client policy should be introduced in the gnutella protocol or standards, etc.

Has you guys notified the other clients too? gtk-gnutella, FrostWire, Shareaza, Morpheus, Phex, KCeasy, etc?

Answer to the first poster's question is, yes.
No adjectives, no modifiers and no qualifiers...
Just plain, yes.

LW is worse now than Shareaza... And THAT takes some doing.

What's your source of information (or at least: could you post some background)?

I don't like hitting people without backup...

Exactly the same observations as noted by LotR, except it is not only very noticeable with Phex but with BS Pro 5.2.5.3 as well.

These are de facto observations, not theories.

Aside re: Shareaza should require no clarification.

I know that LotR has mentioned, in the past, some details of his sharing content but I cannot recall them now...

BUT, I KNOW what my share content is... Variable titles and volume of files but normally about 3,000 eBook files, most of them < 600kb - ONLY eBooks ! This means I do a lot of sharing with very rapid 'turnaround'... Meaning, I share a lot to a lot... Many, many different upload connects... Normally my share volume is a bit above 3GB, but with 3,000 some files that is a VERY different experience than sharing a few .avi files that come to the same overall 'bulk' but very few unique connects.

Believe me... With a sharing base such as I describe, one can see a lot of rogue nonsense going on with various clients... (btw, cleanest and nicest and most perfectly behaved of all is gtk !!!)

(careful with ebooks. I once got sued for sharing a (sadly bad) ebook)

(i2phex is the way to go here...)

So it seems that action will be necessary.