From: slush <slush@centrum•cz>
To: "Jorge Timón" <jtimon@monetize•io>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP0039 Mnemonic code for generating deterministic keys
Date: Thu, 24 Oct 2013 21:37:43 +0200 [thread overview]
Message-ID: <CAJna-Hivko2uGTVWOAkgqCyc9D0LxqNviONpnQ32mPbk18cmyA@mail.gmail.com> (raw)
In-Reply-To: <CAC1+kJPTXOkLoo=QHt1xyNwJ4BkNu1kVOXcZX5gF1MCNMbNSpg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]
On Thu, Oct 24, 2013 at 9:32 PM, Jorge Timón <jtimon@monetize•io> wrote:
> This will probably sound stupid to most of you, but I'll say it anyway.
>
> The aim of mnemonics is to easily remember, isn't it?
>
Well, I would say more "retype" than "remember". I really don't think that
common user will memorize it. But of course, it is still an option.
> But the approach of removing "offensive words" is probably
> counterproductive to achieving that end. These words cause a greater
> emotional impact in our human moral psyches.
>
No, I dont' think it is stupid! Actually it was my concern as well.
Unfortunately I don't think it is "politically correct" to include all
bitches, assholes and motherfuckers in end user product :-).
> If we were willing to use that fact in our advantage to optimize the
> "maximum unforgettableness" criterion, we should actually prefer the
> most generally offensive words in that list. Specially if they can
> combine with each other to produce more offensive results, basically
> the opposite of what we're doing.
> Isn't "legalize murder dirty jew" much easier to remember for most
> people than "sandwich house yellow cauliflower"?
>
>
Well, bip39 can have more dictionaries and *maybe* swearword dictionary
would gain some popularity ;).
slush
[-- Attachment #2: Type: text/html, Size: 2227 bytes --]
prev parent reply other threads:[~2013-10-24 20:06 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
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 [this message]
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=CAJna-Hivko2uGTVWOAkgqCyc9D0LxqNviONpnQ32mPbk18cmyA@mail.gmail.com \
--to=slush@centrum$(echo .)cz \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jtimon@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