[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Library for offload
- From: Max <petersonmaxx@...>
- Date: Thu, 18 Mar 2010 19:56:53 +0100
On Thu, Mar 18, 2010 at 7:47 PM, Xico leite <firstname.lastname@example.org> wrote:
> ---------- Forwarded message ----------
> From: Phoenix Sol <email@example.com>
> Date: 2010/3/18
> To: Lua list <firstname.lastname@example.org>
> On Thu, Mar 18, 2010 at 11:07 AM, steve donovan
> <email@example.com> wrote:
>> On Thu, Mar 18, 2010 at 4:48 PM, Phoenix Sol <firstname.lastname@example.org> wrote:
>>>> link http://offload.sourceforge.net/ and marvel...
>>> Pretty interesting link.
>> Entertaining semantic footwork...but I don't think a hard-nosed court
>> would buy the argument that the plaintiff did not have the copyrighted
>> work, only access to distributed binary chunks.
> My thoughts, more or less exactly... But I'm kind of intrigued about
> it's method of file storage. What are the practical implications of
> breaking up files into shared 'chunks' like that? Better spatial
> efficiency? Crazy processing overhead? Does it have any merit if we
> ignore it's philosophical legal conjecture? (And assuming it's not
> spread out over a bunch of random peecees with miserable upload speeds
Offload is storing files by XORing the file, that means, the chunks
have no relation to the original file.
You just share shreddered blocks in the p2p network. The "meaning" is
in the off-torrent.
gnutella3.sf.net is the lua gui client for it, describing it on the
webpage, that this p2p protocol is mixing all three: gnutella, torrent
and edonkey. Offload has some potentials, as you can download and see
files without any risk to be sued.
Anyone helping in the lua client g3?