๐
Original date posted:2018-01-08
๐ Original message:On Mon, Jan 8, 2018 at 11:34 AM, Greg Sanders via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org> wrote:
> Has anyone actually used the multilingual support in bip39?
>
Copay (and all its clones) use it.
>
> If a feature of the standard has not been(widely?) used in years, and
> isn't supported in any major wallet(?), it seems indicative it was a
> mistake to add it in the first place, since it's a footgun in the making
> for some poor sap who can't even read English letters when almost all
> documentation is written in English.
>
> On Mon, Jan 8, 2018 at 6:13 AM, nullius via bitcoin-dev <
> bitcoin-dev at lists.linuxfoundation.org> wrote:
>
>> On 2018-01-08 at 07:35:52 +0000, ๆจใไธใใใช <kinoshitajona at gmail.com> wrote:
>>
>>> This is very sad.
>>>
>>> The number one problem in Japan with BIP39 seeds is with English words.
>>>
>>> I have seen a 60 year old Japanese man writing down his phrase (because
>>> he kept on failing recovery), and watched him write down "aneter" for
>>> "amateur"...
>>>
>>> [...]
>>>
>>> If you understand English and can spell, you read a word, your brain
>>> processes the word, and you can spell it on your own when writing down.
>>> Not many Japanese people can do that, so they need to copy letter for
>>> letter, taking a long time, and still messing up on occasion.
>>>
>>> [...]
>>>
>>> Defining "everyone should only use English, because ASCII is easier to
>>> plan for" is not a good way to move forward as a currency.
>>>
>>
>> Well said. Thank you for telling of these experiences. Now please,
>> letโs put the shoe on the other foot.
>>
>> I ask everybody who wants an English-only mnemonic standard to entrust
>> *their own money* to their abilities to very, very carefully write this
>> downโthen later, type it back in:
>>
>> ใใใ ใใใ ใใใ ใใใ ใฆใใใ ใใจใ
>> ใจใใ ใฏใใ ใใใใพ ใปใใ ใใกใใฃใต ใใใค
>>
>> (Approximate translation: โWhatever would you do if Bitcoin had been
>> invented by somebody named Satoshi Nakamoto?โ)
>>
>> No, wait: That is only a 12-word mnemonic. We are probably talking
>> about a Trezor; so now, hey you there, stake the backup of your lifeโs
>> savings on your ability to handwrite *this*:
>>
>> ใซใใ ใใฒใใ ใซใใใ ใฒใใ ใใใใ ใใฎใ ใญใใ ใฏใใใ ใฒใใ
>> ใจใใ ใใใใใ ใใชใ ใใชใใช ใซใใใใใใ ใใใ ใใใใ ใฟใใ
>> ใธใใ ใใฒใใ ใใใใฒ ใตใใ ใใใ ใใใใใ ใใใพใ
>>
>> Ready to bet your money on *that* as a backup phrase in your own hands?
>> No? Then please, stop demanding that others risk *their* money on the
>> inverse case.
>>
>> ----
>>
>> If you cheat here by having studied Japanese, then remember that many
>> Japanese people know English and other European languages, too. Then think
>> of how much money would be lost by your non-Japanese-literate family and
>> friendsโif BIP 39 had only Japanese wordlists, and your folks needed to
>> wrestle with the above phrases as their โmnemonicsโ.
>>
>> In such cases, the phrases cannot be called โmnemonicsโ at all. A
>> โmnemonicโ implies aid to memory. Gibberish in a wholly alien writing
>> system is much worse even than transcribing pseudorandom hex strings. The
>> Japanese man in the quoted story, who wrote โaneterโ for โamateurโ, was not
>> dealing with a *mnemonic*: He was using the worldโs most inefficient means
>> of making cryptic bitstrings *less* userfriendly.
>>
>> ----
>>
>> I began this thread with a quite simple request: Is โๆฅๆฌ่ชโ an appropriate
>> string for identifying the Japanese language to Japanese users? And what
>> of the other strings I posted for other languages?
>>
>> I asked this as an implementer working on my own instance of the greatest
>> guard against vendor lock-in and stale software: Independent
>> implementations. โ I asked, because obviously, I myself do not speak all
>> these different languages; and I want to implement them all. *All.*
>>
>> Some replies have been interesting in their own right; but thus far,
>> nobody has squarely addressed the substance of my question.
>>
>> Most worrisome is that much of the discussion has veered into criticism
>> of multi-language support. I opened with a question about other languages,
>> and I am getting replies which raise a hue and cry of โEnglish only!โ
>>
>> Though I am fluent and literate in English, I am uninterested in ever
>> implementing any standard of this nature which is artificially restricted
>> to English. I am fortunate; for as of this moment, we have a standard
>> called โBIP 39โ which has seven non-English wordlists, and four more
>> pending in open pull requests (#432, #442, #493, #621).
>>
>> I request discussion of language identification strings appropriate for
>> use with that standard.
>>
>> (P.S., I hope that my system did not mangle anything in the foregoing. I
>> have seen weird copypaste behaviour mess up decomposed characters. I
>> thought of this after I searched for and collected some visually
>> fascinating phrases; so I tried to normalize these to NFC... It should go
>> without saying, easyseed output the Japanese perfectly!)
>>
>>
>> --
>> nullius at nym.zone | PGP ECC: 0xC2E91CD74A4C57A105F6C21B5A00591B2F307E0C
>> Bitcoin: bc1qcash96s5jqppzsp8hy8swkggf7f6agex98an7h | (Segwit nested:
>> 3NULL3ZCUXr7RDLxXeLPDMZDZYxuaYkCnG) (PGP RSA: 0x36EBB4AB699A10EE)
>> โโIf youโre not doing anything wrong, you have nothing to hide.โ
>> No! Because I do nothing wrong, I have nothing to show.โ โ nullius
>>
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev at lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
>>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
--
Matรญas Alejo Garcia
@ematiu
Roads? Where we're going, we don't need roads!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20180108/eaa842ab/attachment.html>;
Matias Alejo Garcia [ARCHIVE] /
npub1p6โฆ8etde
2023-06-07 20:09:18
in reply to nevent1qโฆth2y
Author Public Key
npub1p6uknnmm7wknvg9cq5wqsf7ulpsrdzd6zt6qw707y5t05fuzvfdsx8etdePublished at
2023-06-07 20:09:18Event JSON
{
"id": "c45bcf03bd3a4c82e4e26f30e34a915b6a1be4f74581e5fd9561f4fb9302f65d",
"pubkey": "0eb969cf7bf3ad3620b8051c0827dcf8603689ba12f40779fe2516fa2782625b",
"created_at": 1686161358,
"kind": 1,
"tags": [
[
"e",
"fe0e5e6b2ee549e4de33e0df2c7264cec2b2f2c4c2ea65f37406e83e8f8c5658",
"",
"root"
],
[
"e",
"769c8afe8dc57873c32fb9ca6f5e2c17cc675db9964bfac0ff35a242b14efd8a",
"",
"reply"
],
[
"p",
"937f10fc4f78d8676348562d9d886843fbb351d99d6c96423fe9970819962e19"
]
],
"content": "๐
Original date posted:2018-01-08\n๐ Original message:On Mon, Jan 8, 2018 at 11:34 AM, Greg Sanders via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e Has anyone actually used the multilingual support in bip39?\n\u003e\n\n\nCopay (and all its clones) use it.\n\n\n\n\n\n\u003e\n\u003e If a feature of the standard has not been(widely?) used in years, and\n\u003e isn't supported in any major wallet(?), it seems indicative it was a\n\u003e mistake to add it in the first place, since it's a footgun in the making\n\u003e for some poor sap who can't even read English letters when almost all\n\u003e documentation is written in English.\n\u003e\n\u003e On Mon, Jan 8, 2018 at 6:13 AM, nullius via bitcoin-dev \u003c\n\u003e bitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\n\u003e\u003e On 2018-01-08 at 07:35:52 +0000, ๆจใไธใใใช \u003ckinoshitajona at gmail.com\u003e wrote:\n\u003e\u003e\n\u003e\u003e\u003e This is very sad.\n\u003e\u003e\u003e\n\u003e\u003e\u003e The number one problem in Japan with BIP39 seeds is with English words.\n\u003e\u003e\u003e\n\u003e\u003e\u003e I have seen a 60 year old Japanese man writing down his phrase (because\n\u003e\u003e\u003e he kept on failing recovery), and watched him write down \"aneter\" for\n\u003e\u003e\u003e \"amateur\"...\n\u003e\u003e\u003e\n\u003e\u003e\u003e [...]\n\u003e\u003e\u003e\n\u003e\u003e\u003e If you understand English and can spell, you read a word, your brain\n\u003e\u003e\u003e processes the word, and you can spell it on your own when writing down.\n\u003e\u003e\u003e Not many Japanese people can do that, so they need to copy letter for\n\u003e\u003e\u003e letter, taking a long time, and still messing up on occasion.\n\u003e\u003e\u003e\n\u003e\u003e\u003e [...]\n\u003e\u003e\u003e\n\u003e\u003e\u003e Defining \"everyone should only use English, because ASCII is easier to\n\u003e\u003e\u003e plan for\" is not a good way to move forward as a currency.\n\u003e\u003e\u003e\n\u003e\u003e\n\u003e\u003e Well said. Thank you for telling of these experiences. Now please,\n\u003e\u003e letโs put the shoe on the other foot.\n\u003e\u003e\n\u003e\u003e I ask everybody who wants an English-only mnemonic standard to entrust\n\u003e\u003e *their own money* to their abilities to very, very carefully write this\n\u003e\u003e downโthen later, type it back in:\n\u003e\u003e\n\u003e\u003e ใใใ ใใใ ใใใ ใใใ ใฆใใใ ใใจใ\n\u003e\u003e ใจใใ ใฏใใ ใใใใพ ใปใใ ใใกใใฃใต ใใใค\n\u003e\u003e\n\u003e\u003e (Approximate translation: โWhatever would you do if Bitcoin had been\n\u003e\u003e invented by somebody named Satoshi Nakamoto?โ)\n\u003e\u003e\n\u003e\u003e No, wait: That is only a 12-word mnemonic. We are probably talking\n\u003e\u003e about a Trezor; so now, hey you there, stake the backup of your lifeโs\n\u003e\u003e savings on your ability to handwrite *this*:\n\u003e\u003e\n\u003e\u003e ใซใใ ใใฒใใ ใซใใใ ใฒใใ ใใใใ ใใฎใ ใญใใ ใฏใใใ ใฒใใ\n\u003e\u003e ใจใใ ใใใใใ ใใชใ ใใชใใช ใซใใใใใใ ใใใ ใใใใ ใฟใใ\n\u003e\u003e ใธใใ ใใฒใใ ใใใใฒ ใตใใ ใใใ ใใใใใ ใใใพใ\n\u003e\u003e\n\u003e\u003e Ready to bet your money on *that* as a backup phrase in your own hands?\n\u003e\u003e No? Then please, stop demanding that others risk *their* money on the\n\u003e\u003e inverse case.\n\u003e\u003e\n\u003e\u003e ----\n\u003e\u003e\n\u003e\u003e If you cheat here by having studied Japanese, then remember that many\n\u003e\u003e Japanese people know English and other European languages, too. Then think\n\u003e\u003e of how much money would be lost by your non-Japanese-literate family and\n\u003e\u003e friendsโif BIP 39 had only Japanese wordlists, and your folks needed to\n\u003e\u003e wrestle with the above phrases as their โmnemonicsโ.\n\u003e\u003e\n\u003e\u003e In such cases, the phrases cannot be called โmnemonicsโ at all. A\n\u003e\u003e โmnemonicโ implies aid to memory. Gibberish in a wholly alien writing\n\u003e\u003e system is much worse even than transcribing pseudorandom hex strings. The\n\u003e\u003e Japanese man in the quoted story, who wrote โaneterโ for โamateurโ, was not\n\u003e\u003e dealing with a *mnemonic*: He was using the worldโs most inefficient means\n\u003e\u003e of making cryptic bitstrings *less* userfriendly.\n\u003e\u003e\n\u003e\u003e ----\n\u003e\u003e\n\u003e\u003e I began this thread with a quite simple request: Is โๆฅๆฌ่ชโ an appropriate\n\u003e\u003e string for identifying the Japanese language to Japanese users? And what\n\u003e\u003e of the other strings I posted for other languages?\n\u003e\u003e\n\u003e\u003e I asked this as an implementer working on my own instance of the greatest\n\u003e\u003e guard against vendor lock-in and stale software: Independent\n\u003e\u003e implementations. โ I asked, because obviously, I myself do not speak all\n\u003e\u003e these different languages; and I want to implement them all. *All.*\n\u003e\u003e\n\u003e\u003e Some replies have been interesting in their own right; but thus far,\n\u003e\u003e nobody has squarely addressed the substance of my question.\n\u003e\u003e\n\u003e\u003e Most worrisome is that much of the discussion has veered into criticism\n\u003e\u003e of multi-language support. I opened with a question about other languages,\n\u003e\u003e and I am getting replies which raise a hue and cry of โEnglish only!โ\n\u003e\u003e\n\u003e\u003e Though I am fluent and literate in English, I am uninterested in ever\n\u003e\u003e implementing any standard of this nature which is artificially restricted\n\u003e\u003e to English. I am fortunate; for as of this moment, we have a standard\n\u003e\u003e called โBIP 39โ which has seven non-English wordlists, and four more\n\u003e\u003e pending in open pull requests (#432, #442, #493, #621).\n\u003e\u003e\n\u003e\u003e I request discussion of language identification strings appropriate for\n\u003e\u003e use with that standard.\n\u003e\u003e\n\u003e\u003e (P.S., I hope that my system did not mangle anything in the foregoing. I\n\u003e\u003e have seen weird copypaste behaviour mess up decomposed characters. I\n\u003e\u003e thought of this after I searched for and collected some visually\n\u003e\u003e fascinating phrases; so I tried to normalize these to NFC... It should go\n\u003e\u003e without saying, easyseed output the Japanese perfectly!)\n\u003e\u003e\n\u003e\u003e\n\u003e\u003e --\n\u003e\u003e nullius at nym.zone | PGP ECC: 0xC2E91CD74A4C57A105F6C21B5A00591B2F307E0C\n\u003e\u003e Bitcoin: bc1qcash96s5jqppzsp8hy8swkggf7f6agex98an7h | (Segwit nested:\n\u003e\u003e 3NULL3ZCUXr7RDLxXeLPDMZDZYxuaYkCnG) (PGP RSA: 0x36EBB4AB699A10EE)\n\u003e\u003e โโIf youโre not doing anything wrong, you have nothing to hide.โ\n\u003e\u003e No! Because I do nothing wrong, I have nothing to show.โ โ nullius\n\u003e\u003e\n\u003e\u003e _______________________________________________\n\u003e\u003e bitcoin-dev mailing list\n\u003e\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\u003e\n\u003e\u003e\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n\u003e\n\n\n-- \nMatรญas Alejo Garcia\n@ematiu\nRoads? Where we're going, we don't need roads!\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20180108/eaa842ab/attachment.html\u003e",
"sig": "5e4e5abc452e01aeef2cddedd9bcd44458f344a0533e5d8c338a7ed2653558161a8d53d57e50cd1d6239ce5f633278e02b56b026d18dc962309971a7b8bb0752"
}