{"type":"rich","version":"1.0","author_name":"npub1s4lj77xuzcu7wy04afcr487f0r3za0f8n2775xrpkld2sv639mjqsd44kw","author_url":"https://nostr.ae/npub1s4lj77xuzcu7wy04afcr487f0r3za0f8n2775xrpkld2sv639mjqsd44kw","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-01-12\n📝 Original message:On Sun, Jan 12, 2014 at 5:33 AM, Jeremy Spilman \u003cjeremy at taplink.co\u003e wrote:\n\n\u003e ...\n\u003e Now, you would need to get two pubkeys to the payer, throw in a prefix to\n\u003e help standardize it, and end up with addresses that could look like (for\n\u003e example):\n\u003e\n\u003e\n\u003e xSTLxsn59oaupR6ZKt2yddQ4dp5hcFinnTWkvsDiXtHgAEDg5ajNVzTY8MMQsmqnEn3ZMKxQzrfC3pDimfTWMkiUb7x3jX3J26JSX\n\u003e\n\u003e tSTLcpwzupCFL3maVZkSiB9ib3BXsCAfkhMLgckQEyoj8Tk83ANzofeuDdbX6bSPqNRfACLLFYK8EwVo1jdjxNDFNDWxhnQiAy4ba\n\u003e\n\nNo, please. Make it easy for non-geeks, extend the payment protocol, or\nwe'll spend the next two years writing code that tries to ignore linebreaks\nand spaces and changing \u003cinput\u003e elements in HTML forms to \u003ctextarea\u003e ....\n\n-- \n--\nGavin Andrese\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140112/4de94ef8/attachment.html\u003e"}