<oembed><type>rich</type><version>1.0</version><author_name>npub1dtr22xd42nv07un2xq0rmtkqkjylgsmexau0anxxafa9xmmn2ncshu7wrs</author_name><author_url>https://nostr.ae/npub1dtr22xd42nv07un2xq0rmtkqkjylgsmexau0anxxafa9xmmn2ncshu7wrs</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2013-11-14&#xA;📝 Original message:On Thursday, November 14, 2013 11:11:26 PM Mark Friedenbach wrote:&#xA;&gt; &#34;key id&#34; (thanks sipa).&#xA;&gt; &#xA;&gt; I know it&#39;s a more technical term, but that is rather the point. It&#xA;&gt; was a fundamental error to call hashed-pubkeys &#34;addresses&#34; as people&#xA;&gt; either associate this with &#34;account&#34; or physical addresses, which also&#xA;&gt; rarely change.&#xA;&gt; &#xA;&gt; Security and privacy guarantees of the system are defeated when key&#xA;&gt; pairs are reused. We should ideally adopt terminology that lead people&#xA;&gt; to associations of ephemeral, temporary use. &#34;key id&#34; is at least&#xA;&gt; neutral in this regard. Can anyone think of something better?&#xA;&#xA;Keys are often reused, so not sure that conveys the single-use much better.&#xA;Reason I suggested invoice id is because nobody wants to pay the same invoice &#xA;twice.&#xA;&#xA;Luke</html></oembed>