[core-dev] Re: [codepatch] Bittorrent v4

Philippe Verdy wrote:
> From: "Greg Bildson" <[email protected]>
> 
>>From: Gregorio Roper
>>
>>>Plus, I'm thinking about extending the protocol a bit, to reduce the
>>>dependency
>>>on Trackers...
>>
>>On the issue of extending the protocol, hopefully we can avoid the hatred
>>that Bram feels towards Shareaza for doing things he didn't like.  It does
>>seem that trackers are a potential central weakness although they appear
> 
> to
> 
>>work well from what I have heard to date.  I've always wanted to have an
>>anchor type capability for magnets/altlocs that would act like a tracker
> 
> for
> 
>>our normal download mesh.  We should probably not try to get to fancy
> 
> though
> 
>>with the BT protocol until we have the standard version 100% sturdy and we
>>generate some trust in the BT community.  These all appear to be important
>>things based on past experience.
> 
> 
> I really do agree there. Before starting doing facy things in BT, let's
> first start with its basic protocol, and say a graceful "hello, LimeWire is
> there too!" to the BT community.
> 
> Does this community exist somewhere? Shouldn't we announce us to them, and
> look for their influent members, to start collaborating long before we
> introduce our new features? There's probably a GDF-like group for BitTorrent
> developers, and some good practices and policies to learn and negociate with
> them, plus some "certification process" to demonstrate that LimeWire will
> act responsibly regarding this protocol.
> 
> The most important thing to keep in mind is that LimeWire should not leach
> BT sources too much, the issue being that LimeWire will have difficulties to
> act as a tracker for new contents, and that LimeWire must keep the torrent
> active for enough time after download completes, meaning that it must
> dedicate a significant bandwidth to other BT-only clients...

There is such a BT community but you cannot really compare it to the GDF. They 
are using the [email protected] mailinglist. There is no "certification 
process" or the like.

I will not implement the server side of the tracker protocol, nor do I plan on 
adding a feature for releasing torrents. If LimeWire users want to publish 
content they can already use magnet links.

My BT implementation tries to upload as much as it downloads before 
automatically closing the torrent and it dedicates a certain part of its 
bandwidth to torrent uploads. The bandwidth management I am using guarantees a 
certain part of the upstream to BT.

And really, other BT clients will definitely stay completely unaware of any 
extension that I might add the infrastructure for, - unless they used a LimeWire 
peer ID ("LIME" + LimeWire GUID) which should be quite difficult to create by 
chance.

mfg
gregorio
_______________________________________________
core-dev mailing list
[email protected]
http://www.limewire.org/mailman/listinfo/core-dev