X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 7D551D1CA01; Tue, 4 Nov 2003 20:54:13 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 74950-06; Tue, 4 Nov 2003 16:53:43 -0400 (AST) Received: from ganymede.hub.org (u46n208.hfx.eastlink.ca [24.222.46.208]) by svr1.postgresql.org (Postfix) with ESMTP id 7A141D1CA02; Tue, 4 Nov 2003 16:53:21 -0400 (AST) Received: by ganymede.hub.org (Postfix, from userid 1000) id 9FB1E35D00; Tue, 4 Nov 2003 16:52:16 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 928DB35B54; Tue, 4 Nov 2003 16:52:16 -0400 (AST) Date: Tue, 4 Nov 2003 16:52:16 -0400 (AST) From: "Marc G. Fournier" X-X-Sender: scrappy@ganymede.hub.org To: Bruce Momjian Cc: josh@agliodbs.com, "Marc G. Fournier" , pgsql-www@postgresql.org, pgsql-core@postgresql.org Subject: Re: [CORE] Bittorrent? In-Reply-To: <200311042037.hA4KbR303674@candle.pha.pa.us> Message-ID: <20031104165129.M24889@ganymede.hub.org> References: <200311042037.hA4KbR303674@candle.pha.pa.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/14 X-Sequence-Number: 2661 On Tue, 4 Nov 2003, Bruce Momjian wrote: > Josh Berkus wrote: > > Marc, > > > > > If I'm reading the FAQ/Documentation correctly ... and I may not be > > > understanding it completely after a admittedly quick pursual ... it sounds > > > like a 'napster for files', with ppl uploading to our servers, as well as > > > downloading from it? > > > > Yes, but they're OSS-friendly, popular, and several members of our community > > already use Bitorrent. Among other things, Linux kernels get distributed > > over it. It uses the p2p network to bypass bottlenecks at certain ftp sites, > > allowing you to stream the same download from 2-5 sites simultaneosly and > > saturate your download bandwidth. > > > > I don't think we necessarily need to host a Bitorrent server at hub.org; I'm > > not clear on how joining bitorrent works, really. I'll ask one of the > > current users. > > What if someone adds a trojan to the source and puts it on Bitorrent? > Doesn't seem like something we should do lightly. That one isn't so big a deal, as we could easily made the 'official md5 hashes' available on the web site, which is easier to access then the ftp server(s) ... then the oneous(sp?) is on the downloader to confirm that the md5's check out okay ...