Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VJWfD-00088m-FT for bitcoin-development@lists.sourceforge.net; Tue, 10 Sep 2013 22:44:03 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.217.178 as permitted sender) client-ip=209.85.217.178; envelope-from=gmaxwell@gmail.com; helo=mail-lb0-f178.google.com; Received: from mail-lb0-f178.google.com ([209.85.217.178]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VJWfC-0003kd-KV for bitcoin-development@lists.sourceforge.net; Tue, 10 Sep 2013 22:44:03 +0000 Received: by mail-lb0-f178.google.com with SMTP id z5so6694159lbh.23 for ; Tue, 10 Sep 2013 15:43:55 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.112.210.66 with SMTP id ms2mr66693lbc.51.1378853035585; Tue, 10 Sep 2013 15:43:55 -0700 (PDT) Received: by 10.112.89.72 with HTTP; Tue, 10 Sep 2013 15:43:55 -0700 (PDT) In-Reply-To: <522F9EC9.7020008@monetize.io> References: <796AC330-56EF-43D2-9935-5409824A4F33@godofgod.co.uk> <0F445FFE-FA1A-4A64-9A28-C734E744B5F7@godofgod.co.uk> <522F9EC9.7020008@monetize.io> Date: Tue, 10 Sep 2013 15:43:55 -0700 Message-ID: From: Gregory Maxwell To: Mark Friedenbach Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gmaxwell[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1VJWfC-0003kd-KV Cc: Bitcoin Development Subject: Re: [Bitcoin-development] BIP0039 Mnemonic code for generating deterministic keys X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Sep 2013 22:44:03 -0000 On Tue, Sep 10, 2013 at 3:35 PM, Mark Friedenbach wrote: > It can really backfire to get one of these things wrong. On the subject of unexpected results, for the longest time wikipedia had problems with images randomly not displaying for some users. Images were stored by their cryptographic hash. If the hash was deadbeef the URL would be: /d/de/deadbeef.jpg Turns out that a lot of people are running addons that block /a/ad/ ... Not running afoul of various censorware filters should be a design target too, as insane as it seems. Simply because "The key is 'Tienanmen Square people monkey'" "People monkey isn't working!" is a hard situation to trouble shoot!