<oembed><type>rich</type><version>1.0</version><author_name>npub12rkw0jajmsck4uwdtksdvtswrlkypusfryjzera7m4fhqta6jhdsz3aqxc</author_name><author_url>https://nostr.ae/npub12rkw0jajmsck4uwdtksdvtswrlkypusfryjzera7m4fhqta6jhdsz3aqxc</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2013-11-15&#xA;📝 Original message:On 16 November 2013 01:10, Luke-Jr &lt;luke at dashjr.org&gt; wrote:&#xA;&#xA;&gt; On Saturday, November 16, 2013 12:41:56 AM Drak wrote:&#xA;&gt; &gt; So &#34;a payment clears after one confirmation, but you might want to wait&#xA;&gt; &gt; until the payment has been confirmed n times&#34;.&#xA;&gt; &gt; Then at least you are not using the same word for two different meanings&#xA;&gt; &gt; and you&#39;re using stuff more familiar in popular lexicon.&#xA;&gt; &gt; I dont think it&#39;s helpful for users if we use the word &#34;blocks&#34;.&#xA;&gt;&#xA;&gt; &#34;Confirmations&#34; in a numeric context isn&#39;t correct, though. We&#39;re using to&#xA;&gt; it&#xA;&gt; because we&#39;ve been using Bitcoin so long, but to the average person they&#xA;&gt; would&#xA;&gt; expect it to mean something more than it is. If not referring to blocks,&#xA;&gt; then&#xA;&gt; perhaps &#34;witnessed N times&#34;?&#xA;&#xA;&#xA;If you are talking about user interface, I don&#39;t think you have to be&#xA;technically correct. It must make sense to the user.&#xA;A user cares about his balance, and did a payment &#34;go through&#34;, and &#34;did my&#xA;payment arrive/clear&#34;.&#xA;&#xA;The UI is for their benefit.&#xA;&#xA;&#xA;&gt; &gt; For years, people had a problem with  &#34;email address&#34;, instead using&#xA;&gt; &#34;email&#xA;&gt; &gt; number&#34; but they got there eventually. Most people nowadays use &#34;email&#xA;&gt; &gt; address&#34;&#xA;&gt; &gt; So &#34;payment address&#34; or &#34;bitcoin address&#34; make better sense here when&#xA;&gt; &gt; qualified as a &#34;&lt;foo&gt; address&#34; and not just an &#34;address&#34;&#xA;&gt; &gt;&#xA;&gt; &gt; You could also call it &#34;payment id&#34;, but I dont think &#34;invoice id&#34; since&#xA;&gt; &gt; no-one pays to an invoice id that&#39;s just a reference for a payment, not&#xA;&gt; the&#xA;&gt; &gt; destination.&#xA;&gt; &gt;&#xA;&gt; &gt; People are very familiar with Paypal these days, and are familiar with&#xA;&gt; &gt; &#34;paypal address&#34; or their &#34;paypal id&#34; so again I think valid contenders&#xA;&gt; are&#xA;&gt; &gt; &#34;bitcoin address&#34; or &#34;bitcoin id&#34;.&#xA;&gt;&#xA;&gt; I think you might be demonstrating my point with regard to user confusion&#xA;&gt; here. Bitcoin addresses are *not* like email addresses, paypal ids, etc.&#xA;&gt; Bitcoin addresses aren&#39;t the destination - they&#39;re point to a destination&#xA;&gt; (an&#xA;&gt; account in a wallet), but they also represent information such as who is&#xA;&gt; paying and what for - in other words, a specific invoice.&#xA;&#xA;&#xA;Maybe, but again from the user&#39;s perspective they pay someone, and they&#xA;receive money - just like you do with paypal using an email address.&#xA;The technical bits in the middle dont matter to the user and trying to crap&#xA;stuff in to be technically correct is just confusing to them.&#xA;&#xA;The UI needs to be about the user and fit with his experience of the world.&#xA;&#xA;Drak&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20131116/49a7ee31/attachment.html&gt;</html></oembed>