From: Mike Hearn <mike@plan99.net>
To: Daniel F <nanotube@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposal: MultiBit as default desktop client on bitcoin.org
Date: Tue, 9 Jul 2013 17:27:17 +0200 [thread overview]
Message-ID: <CANEZrP2mTgR64mXzKWQB6sPj=cHz9VcOuqqNO=0H2mrgWn2Q6Q@mail.gmail.com> (raw)
In-Reply-To: <51DC24DE.2040801@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1455 bytes --]
That's true - we could serve new users off our own servers and auto updates
off SF.net mirrors, potentially.
On Tue, Jul 9, 2013 at 4:57 PM, Daniel F <nanotube@gmail.com> wrote:
> on 07/09/2013 10:28 AM Mike Hearn said the following:
> > SourceForge has a horrible UI and blocks some countries. It also exposes
> > us to a large and potentially hackable mirror network. Whilst we're not
> > bandwidth constrained on our own servers, let's try and keep using them.
>
> the point was just that "if need be" free capacity is available without
> having to throw money at it. until there's no need, doesn't matter.
>
> also hackability (and ui) should be irrelevant for the autoupdate
> process (which i presume will do all kinds of checksum and sig
> verification). and it's likely the autoupdates that will create very
> lumpy download demand.
>
>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
[-- Attachment #2: Type: text/html, Size: 2212 bytes --]
next prev parent reply other threads:[~2013-07-09 15:27 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
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 [this message]
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='CANEZrP2mTgR64mXzKWQB6sPj=cHz9VcOuqqNO=0H2mrgWn2Q6Q@mail.gmail.com' \
--to=mike@plan99.net \
--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