Domain: clip2.com
Stories and comments across the archive that link to clip2.com.
Comments · 9
-
Re:Gnutella is non-proprietary
This can easily be done, you just have to make sure that more people use software like Clip2 Reflector that makes Gnutella more scaleable. I could easily see Morpheus creating there own version of Reflector that's bolted onto a Gnutella client so that unsuspecting broadband users will turn their computers into "superpeers".
Too bad that according to this page Clip2 reflector seems to have mysteriously disappeared.
-
This is already being done..
Go download your favorite Gnutella-based client program, connect, and do a search for the porn of your choice. It's so easy to amass gigabytes of mpegs that it's a wonder people will actually pay to visit x-rated websites. There are also centralized filesharing programs (FileNavigator) which will allow you to trade video with others who are also connecting to various OpenNap servers.
Very informative peer-to-peer links:
www.clip2.com
www.infoanarchy.org
From these places you can audit various downloadables as well as read the latest p2p news. -
Peer to Peer works with a list of serversAll you need is a web page with a list of servers. Once you connect to one server on the network it tells about its peers, and they tell you about their peers, and so on, and so on.
Maybe they'll shut down one web page, but they can't get them all at once.
Couple of links to check out:
Gnutella host caches
Clip2 Super Peers -
Client Interoperabilty
The problem I see is not whether the protocol itself can scale, we are seeing numerous "tweaks" that will allow this ( Clip2's Reflector and Bearshare.net's forthcoming 3.0.0 "Defender" release) What I see as the problem is the splintering and added features being incorporated by the different Gnutella Clients: Gnotella has added "Improved bitrate scanning", BearShare and Limewire's Firewall Detection, as well as other "extraneous" features, that add information to the gnutella packets. How long will it be before these clients cause sufficient incompatibility that seperate, client specific networks arise? What we really need is an agreement between the different developers to pass on these extra packets, or agree on a central "feature set". I am not advocating that we do away with the myriad gnutella clinets, I think there variety and different personalities are great. I just don't want to see the community splinter through incompatibility issues.
-OctaneZ
(What I would really like to see is a native applications similar to Clip2's reflector for both WIN32 and Linux that serves as a "network server" only, that uses low CPU and large numbers of connections for people who believe in the Gnutella idea and are graced with highspeed connections.) -
Re:Gnutella isn't the answer
I think the answer is something along the lines of the Reflector strategy being devloped here. A good idea, but not quite stable enough to keep up for extended periods (yet). Give it a read-thru and see if it doesn't address the issue quite well.
-
It's overly optimistic.I saw no analysis of the fact that multiple computers I am connected to will be connected to each other. I believe the paper essentially looks at gnutella as a tree with the searcher at the root. This is clearly wrong. I believe that the result of this is: less bandwidth per search due to repeated queries being dropped, and less hosts reachable due to fewer new nodes at each level out. However, it actually makes things worse, because a node may recieve a query multiple times, it just won't pass it on more than once. SO, bandwidth per search per node hit by search goes up. It scales WORSE thn predicted.
Also, this means that the population P DOES have an effect on the number of reachable users, because as P increases the number of redundant connections will decrease. Don't have the math to prove it, but I think that's the way it works.
Also, is there analysis of why gnutella can't scale in terms of P? I can see why it won't scale in terms of number of users I can reach, but why not in total users, IF users are content to let themselves be limited to a small fraction of the network (this should be enforced by the clients. I know people can wrte their own, but they shouldn't write them to allow huge TTLs).
Also, what of the reflectors?
-
Germany, Japan, Canada
I wonder why Germany ranks highest among the non-US users... Japan I can see and Canada is in North America but why Germany? Check out this graphic.
There are some cool charts examining the .net breakdown (remember that cool poster from ThinkGeek?) and the breakdown by .edu as well.
-Duke
-
Germany, Japan, Canada
I wonder why Germany ranks highest among the non-US users... Japan I can see and Canada is in North America but why Germany? Check out this graphic.
There are some cool charts examining the .net breakdown (remember that cool poster from ThinkGeek?) and the breakdown by .edu as well.
-Duke
-
Germany, Japan, Canada
I wonder why Germany ranks highest among the non-US users... Japan I can see and Canada is in North America but why Germany? Check out this graphic.
There are some cool charts examining the .net breakdown (remember that cool poster from ThinkGeek?) and the breakdown by .edu as well.
-Duke