From: Gregory Maxwell <gmaxwell@gmail•com>
To: Mark Friedenbach <mark@monetize•io>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP0039 Mnemonic code for generating deterministic keys
Date: Tue, 10 Sep 2013 15:43:55 -0700 [thread overview]
Message-ID: <CAAS2fgSc=k-vKk=1xfCeohtTspmjqx9VT3C6nu_OqKVtecbyJg@mail.gmail.com> (raw)
In-Reply-To: <522F9EC9.7020008@monetize.io>
On Tue, Sep 10, 2013 at 3:35 PM, Mark Friedenbach <mark@monetize•io> 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!
next prev parent reply other threads:[~2013-09-10 22:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 16:44 slush
2013-09-10 17:36 ` Andreas M. Antonopoulos
2013-09-10 20:40 ` Matthew Mitchell
2013-09-10 20:50 ` slush
2013-09-10 21:03 ` Matthew Mitchell
2013-09-10 21:34 ` Pavol Rusnak
2013-09-10 22:08 ` Gregory Maxwell
2013-09-10 22:35 ` Mark Friedenbach
2013-09-10 22:43 ` Gregory Maxwell [this message]
2013-09-11 12:49 ` Andreas Petersson
2013-09-12 12:09 ` Pavol Rusnak
2013-09-10 22:47 ` slush
2013-09-12 12:11 ` Pavol Rusnak
2013-09-12 16:02 ` Matthew Mitchell
2013-10-24 18:26 ` slush
2013-10-24 19:23 ` Pieter Wuille
2013-10-24 19:46 ` slush
2013-10-24 19:32 ` Jorge Timón
2013-10-24 19:37 ` slush
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='CAAS2fgSc=k-vKk=1xfCeohtTspmjqx9VT3C6nu_OqKVtecbyJg@mail.gmail.com' \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mark@monetize$(echo .)io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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