Quote:
Originally posted by Abaris You did not get my point. The Bearshares are clustered together, but the bearshare cluster as a whole is still perfectly connected to the gnutella sphere.that means every XoloX client can connect to a Gnucleus or LimeWire client that is connected to Bearshare. Therefore, search packets of one of them do reach the other, and indeed, Bearshare and XoloX clients CAN download from each other. |
OK, apart from those bearshares that are too many hops from the edge of the bearshare cloud. But I take your point.
Quote:
What you are doing is a completely other thing. You do not block Bearshare. |
Well, there are too different things going on in that opensourcep2p gnucleus client.
I haven't seen it, but I understand that one option is to stay on gnutella and just block on an ID basis, eg user can choose just bearshare, or as Anonnn urges on the web page, block all commercial vendors, or whatever they like. I believe the user types in the string.
The other option is use the other 'network' or 'opensource' which should be enough to block any non-configured client, but in practice I don't think this is proven. So in addition the gnucleus client blocks all the known commercial clietns based on vendor id.
I think that option 1 is a side-effect of the lack of certainty about the effectiveness of the strategy of changing the connect string header. And since it needed to be implemented to block fully on the opensource network, the 'extra benefit' is that it can be employed on the gnutella network as well with no extra programming effort. So he let the user decide.
Quote:
If you only did that, i wouldn't have said anything. You guys are creating a totally different network, thereby blocking 'every gnutella user who is not willing to join your ideological crusade. |
So now you are arguing against the second network - the second network doesn't block anyone from using the original gnutella network. It leaves the original gnutella network intact, save for the loss of users, who maybe would leave anyway. It is arguable.
Quote:
by blocking one or two clients, like vinnie does, the network as a whole stays perfectly connected.how many clients do you think you are blocking? |
Well, in one case, the gnutella network, it is up to the user, could be any number. I think probably only BS, MRPH, LW at the most, mainly just BS.
Quote:
counting all the discontinued and experimental ones, and every noncommercial client that is not opensource, i guess it will be about ten different clients. |
On the new opensourcep2p network, at the moment, probably right. I doubt that there are that many users on that network anyway. [wildly speculative mode]Interestingly the <A HREF="http://www.limewire.com/index.jsp/size">graph at limewire.com</A> does show a drop around the 20th March when Anonnn launched the idea, of around 50k users .. but I think this must be coisncidence - gnutellaforums didn't get 50k readers that day. There is already a decline evident preceding that date, I'd say about 40k users over half a week immediately before his announcement. This is followed by the sharp drop of another ~50k at 20th March, and it has been more or less stable since then.[/wildly speculative mode]
Maybe the decline of 40k users in half a week would have continued had Anonnn not made his interesting announcement? Who can say?
[QUOTE]
for what reason?
<snip snip snip>[/QUOTE
Reasons covered earlier in debate and on <A HREF="http://opensourcep2p.sourceforge.net/">website</A>.
Quote:
they create clustered subspheres, right. but they still stay connected. and there is no proof at all that they take files away from other vendors and clients. actually, using gnucleus, i happened to download from bearshare at multiple times. |
Yes, I can download from BS using non-BS clients, it's good. On the other hand, some clients have such little success now (read '0.4') that I don't bother using them. And that was a sudden change. I think perhaps driven as much by limewire as BS the date corresponds more with the introduction of ultrapeers AFAICT. I don't really know.
So I don't know, it seems to me a good many of the older clients are blocked from the gnutella network. I think if the opensourcep2p idea isn't killed quickly that people will alter a lot of the older clients to use that network - after all the older and simpler the client is the easier it would be to change. Maybe more clients will work successfully on the opensource network than work successfully on the gnutella network.
Quote:
please, nos, do not tell me what i should be happy for. |
OK, I didn't mean you specifically, I meant the gnutella community in general should at least take some comfort from the fact that we want to keep improving the (opensource) gnutella clients and protocol, even though we don't want to connect to the existing commercial clients any more.
Nos