Bearshare is no longer the dominant client on the network, I say BLOCK IT!
Gnucleus is cool and open source and rules the world!
Gnucleus RULES! COOL!!!

We are free of vinnie at last! PARTY!!

Someone provide a copy of a modified Gnucleus that blocks all this BS on the network. Just like "clean limewire". John should provide a feature to block any client we so chose, give us a little edit box john! GIVE US CHOICE!

I don't want to be part of the BS network! I don't want to share to BS clients and support Vinnie$$$Net!

Vinnie has always wanted his own little network to control and rule over, good riddance! BYE BYE!! Clustering my ****... Cutting off XolX because you want to rule the world, screw you!! there are consequences to your actions vinnie!

Anyone willing to provide the download space? Who is the clean limewire guy?

New connect string for BS clients

VINNIE$$$NET CONNECT/0.6 OK

So it really is a BearShare network, Gnutella is now dead.
"it will be the responsibility of other vendors to crawl our BearShare network and mix in the IP
addresses of our Ultrapeers, if they wish to remain connected to the BearShare network."

I don't know about you but I won't be "crawling" the bearshare network, Vinnie will be crawling back after his bankruptcy since gnutella cut him off.

the_gdf
6308 From: freepeers info@f...
Date: Wed Mar 13, 2002 5:24pm
Subject: Split Networks (Was Re: Don't cooperate...)

> -----Original Message-----
> From: Justin Chapweske [mailto:justin@c...]
>
> I'm curious, but what if anything keeps the LW and BS clusters from
> splitting into two completely seperate networks? Does either LW or
BS
> maintain a probability of connecting to nodes from other vendors to
> prevent a gnutella net split?

BearShare will never drop a connection once it has handshaked and
been accepted. So if a non BearShare host makes it in to a BearShare
host it will stay as long as it wants to, assuming the BearShare host
does not exit the application.

Our improved host cache will visit other host caches (this includes
the Morpheus host caches, currently running BearShare in anchor
mode), storing the IP addresses in a "seed list".

When a BearShare host visits our host cache, we will deliver 30 pongs:

- 18 pongs randomly chosen from the top 50% of hosts measured by
uptime

- 9 pongs randomly chosen from the bottom 50% of hosts measured by
uptime

- 3 pongs randomly selected from the "seed list"

These numbers may be tweaked in the future for optimium network
structure.

When we eliminate our host cache, it will be the responsibility of
other vendors to crawl our BearShare network and mix in the IP
addresses of our Ultrapeers, if they wish to remain connected to the
BearShare network.

Alternatively, we can publish the IP addresses of the top BearShare
hosts measured by uptimes on a web page. Other vendors can include
this list with their installer so their servent can bootstrap from
it, or they can harvest this list periodically and merge the
addresses into their host cache.

Therefore, we have solutions for keeping the network together today,
tomorrow, and beyond (when host caches disappear).

Hmm...

I wonder why no one of the GDF developers say something!

If Gnutella follow this way - I will leave...

Morgwen

The GDF = some high society pals holding each other's hand and controlled by bearshare and limewire. they don't need anyone else, because (they think) they're doing such an excellent work.

Now that a open source client is the #1 client they see their market share going bye bye and they will do anything to keep their "job". Greed doesn't belong on gnutella and this is another example.
gdf isn't controlled by them because they just do whatever they want regardless of what anyone says there.

From the "BearShare 2.5.0 beta 10" message

"- BearShare preferencing, ie. last host slot is reserved for a bear. "

beta 10? Why do they have to announce every release like it's something great and now every beta?

beta 1 - one new feature that no one cares about
beta 2 - fixed bug with the last feature I added
beta 3 - wow! I really messed up and fixed it
beta 4 - ok I think I got it right this time
beta 5 - no really, I got it
(no announcement) took out the feature because I suck as a programmer and can't get this right
beta 7 - patched windows so I can actually make this work
beta 8 - waiting for billy boy gates to accept my patch and sell a new version of windows
beaa 9 - I just wanted some free publicity, no real changes here
beta 10 - hey its your daily update!

Its the vinnie net!

How does the BearShare hostcache know what client is connecting to it? If it only goes by the little four letter ID thingy, I forgot exactly what it's called, it wouldn't be that hard to modify a client to lie to the BearShare hostcache and say it is BearShare. This would completely defeat Vinnie's domination plan.

i think that Bearshare... when connects to another client sends some private data that only bearshare clients understand and respond to.

All you would need to do is use a packet sniffer to examine what it sends out, and emulate it.

Anyone remember the spy packets that bearshare sent out? Remember how vinnie said they were just so he could send out update messages for new versions?
Bearshare has a built in browser and goes directly to the bearshare site trying to sell you t-shrits or other garbage.
Updates and or update messages could easily come in at that time from his home page.

So why are spy packets still being sent????

And, what could be worse than a closed source client that "checks in to the home site" every time you use it?
Do you know what info he sends out to his site when he connects? Is it in a encrypted packet?

Would Vinnie give the RIAA your personal info if threatened with a law suit? YOU BET HE WOULD! $$$

One more good reason to stick with free, spyware free, open source clients.