public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@bitpay.com>
To: Daniel F <nanotube@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Proposal: MultiBit as default desktop client on bitcoin.org
Date: Tue, 9 Jul 2013 10:06:47 -0400	[thread overview]
Message-ID: <CAJHLa0P5D2W_5GH9PGk4wgi2DwsqHjRQkjHZ3uCVwaFNDcPThw@mail.gmail.com> (raw)
In-Reply-To: <51DC1761.5080303@gmail.com>

On Tue, Jul 9, 2013 at 10:00 AM, Daniel F <nanotube@gmail.com> wrote:
> on 07/09/2013 06:56 AM Jim said the following:
>> + it will bump up the MultiBit download from about 11MB to 30-40MB
>> (I think). This drops the maximum copies of MultiBit the multibit.org
>> server can deliver per day from around 90,000 to 30,000ish.
>> The multibit.org server maxes out at 1 TB of bandwidth per day.
>
> You could host your downloads on sourceforge and achieve virtually
> unlimited capacity.

Indeed.  There is no reason to worry about download bandwidth these
days, for open source software downloads.

Move the downloads to a site where such worries do not exist.

-- 
Jeff Garzik
Senior Software Engineer and open source evangelist
BitPay, Inc.      https://bitpay.com/



  reply	other threads:[~2013-07-09 14:06 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 17:10 [Bitcoin-development] Proposal: MultiBit as default desktop client on bitcoin.org Jim
2013-06-27 17:30 ` Jeff Garzik
2013-06-27 18:04   ` Luke-Jr
2013-06-27 18:41     ` Gregory Maxwell
2013-06-27 19:18       ` Jim
2013-06-27 19:40         ` Jim
2013-06-27 19:50           ` Jim
2013-06-27 21:12         ` Alex Kravets
2013-06-27 21:56           ` Jeff Garzik
2013-06-27 22:53             ` Alex Kravets
2013-06-27 22:03           ` Gary Rowe
2013-06-28 10:59       ` John Dillon
2013-06-28  9:10   ` Mike Hearn
2013-06-28 14:24     ` Gavin Andresen
     [not found]       ` <CAFtwHRewE0wgvWsf-785hpCb8ns7wiGaKHAQ-1QmDD-W+diBJA@mail.gmail.com>
2013-06-28 20:37         ` Bill Hees
2013-06-28 20:42           ` Jim
2013-06-30 11:42       ` Mike Hearn
2013-06-30 15:19         ` Jim
2013-06-30 16:39           ` Gary Rowe
2013-07-09  0:22             ` Robert Backhaus
2013-07-09  1:20               ` Caleb James DeLisle
2013-07-09 10:36                 ` Mike Hearn
2013-07-09 10:56                   ` Jim
2013-07-09 11:04                     ` Mike Hearn
2013-07-09 11:13                       ` Will
2013-07-09 11:15                       ` Jim
2013-07-09 11:18                       ` Mike Hearn
2013-07-09 14:00                     ` Daniel F
2013-07-09 14:06                       ` Jeff Garzik [this message]
2013-07-09 14:28                         ` Mike Hearn
2013-07-09 14:46                           ` Jim
2013-07-09 14:57                           ` Daniel F
2013-07-09 15:27                             ` Mike Hearn
2013-07-09 15:32                               ` Nick Simpson
2013-07-09 15:51                                 ` Johnathan Corgan
2013-07-09 16:44                                   ` Mike Hearn
2013-07-09 15:59                                 ` Jeff Garzik
2013-07-09 16:03                                   ` Nick Simpson
2013-07-09 22:15                                   ` Andreas Petersson
2013-06-27 17:56 ` Gregory Maxwell
2013-06-27 18:05   ` Alex Kravets
2013-06-27 23:45   ` Caleb James DeLisle
2013-06-28  9:05   ` Mike Hearn
2013-06-28 10:09     ` John Dillon
2013-06-28 10:20       ` Mike Hearn
2013-06-28 10:32         ` John Dillon
2013-06-30 10:12       ` Peter Todd

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJHLa0P5D2W_5GH9PGk4wgi2DwsqHjRQkjHZ3uCVwaFNDcPThw@mail.gmail.com \
    --to=jgarzik@bitpay.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=nanotube@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox