<oembed><type>rich</type><version>1.0</version><author_name>npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7</author_name><author_url>https://nostr.ae/npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-03-12&#xA;📝 Original message:For reasonably skilled users your points are valid, but I&#39;m sure you&#xA;also – like me – encountered the kind of user who has absolutely no clue&#xA;but thinks he understands. S/he will ignore warnings and run into&#xA;troubles. This generates a huge amount of support cases and likely tears&#xA;about lost coins.&#xA;&#xA;The simple fact that someone elses broken RNG implementation/wrapper&#xA;could compromise the security of my software frightens me.&#xA;&#xA;&#xA;On 03/11/2015 08:04 PM, Jim wrote:&#xA;&gt; The wallet words system isn&#39;t perfect for sure but it does help the user in two main ways:&#xA;&gt; 1) Assuming wallet devs ensure forward compatibility for _their_ wallet the user knows they can recover their bitcoins using the same wallet software in case of a Bad Thing Happening.&#xA;&gt; 2) To an imperfect degree, they can transfer/ recover their bitcoins that are stored in Wallet X into Wallet Y. We need to give them guidance on how to do this.&#xA;&gt; &#xA;&gt; I think it is up to each wallet team to explain to their users clearly how they can do this in their help. It&#39;s only good manners to show your guests where the fire exits are.&#xA;&gt; &#xA;&gt; It can be a simple help page saying:&#xA;&gt; &#34;If you want to transfer your bitcoin out of MultiBit HD to Lighthouse, do this, this and this.&#xA;&gt; If you want to use the Trezor wallet you created in MultiBit HD on myTrezor.com, do this, this and this.&#34;&#xA;&gt; &#xA;&gt; That way users have clear instructions on how to recover their bitcoins.&#xA;&gt; Users don&#39;t care about BIP this or BIP that but they REALLY DO CARE about keeping their bitcoins.&#xA;&gt;</html></oembed>