G2 Support
 

Please tell me in an upcoming version Phex will have G2 Support. That would be really cool, especially if you could choose wich nets you want on. G1, G2 or both. I hope it is coming :D

I sure hope not, work can be much better spent on the Gnutella implementation :o

Its not coming.

Ok then :)

As somebody who runs 24/7 on both Gnutella and G2 (using Shareaza, BearShare, Limewire, just downloaded Phex), I welcome Phex downloads.

However, there have been reports that Phex is leeching by spoofing G2 headers. If Phex isn't going to support G2, that's cool, it's obviously up to GregorK, but it's not kosher to spoof the headers. Shareazas that don't have Gnutella support turned on can't download from Phex users, and the ones that can download from Phex users, you should be able to DL from the same as any other Gnutella client. Personally, I see about 80% of my uploads go to Gnutella, which is fine with me so long as the Gnutella clients play nice.

Thanks for your consideration. Hi, ev!

haha, welcome deltagamma! If what you say is true, you are right, Phex shouldn't spoof G2 headers to get more sources. Most G2 sources are slow anyway, there is not much to gain, but more importantly, that's not ethical.

Ciao :p

Phex supports all headers necessary to download from sources that are in Gnutella search results, in Gnutella download mesh and it downloads from everybody who tries to download partial files from Phex.

Since I assume no MP/G2 nodes are in Gnutella search results, Gnutella download mesh and they wont download partial files from Phex everything should be just fine....

Merci for the clarification Gregork, I guess those were rumors only ;)

Hi GregorK.
I noticed some interesting behavour with phex what the source code seems to back up. It does actually appear that whenever phex has to deal with a shareaza client - it sends the "X-Features: g2/1.0" header.
As you said yourself in this thread, phex will not support G2 so I don't see why the client should send that header to all shareaza clients - regardless of whether the shareaza client is on the Gnutella network or the G2 network.
I recompiled the phex code to not send that header and I could successfully download from shareaza clients when they had Gnutella enabled. When shareaza does not have Gnutella enabled it will not download from phex.
While shareaza does not download from phex when Gnutella is disabled, phex can still download from shareaza.
Why forge the X-Features: g2 header when phex clients will be able to download from shareaza clients on Gnutella. By forging that header it allows phex clients to leech from G2 only shareazas (download from and not upload back)?

Like I said:

Since I assume no MP/G2 nodes are in Gnutella search results, Gnutella download mesh and they wont download partial files from Phex everything should be just fine....

In case Shareaza is leeching partial file downloads, polluting search results or infecting the download mesh Phex is using it to download, which in my eyes is perfectly legitimate.

But since Phex is not supporting G2 and it should never see any G2 search results or G2 sources in download mesh, it should never happen that a G2 node is in Phex download candidates. So this is just a theoretical assumption that Phex could download from a G2 node.

If this still happens to you... Shareaza should better stop polluting Gnutella...!

BTW: You will find the same logic in many other Gnutella clients.