{"type":"rich","version":"1.0","author_name":"npub1xqshkqv2g7uea4xzqwvmgjcz7u8vfavw6aazs999v0azsv3w7u3qpymc2p","author_url":"https://nostr.ae/npub1xqshkqv2g7uea4xzqwvmgjcz7u8vfavw6aazs999v0azsv3w7u3qpymc2p","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2011-12-17\n🗒️ Summary of this message: Luke-Jr suggests standardizing and supporting public key addresses, despite their length, for better QR code compatibility and shorter transactions in blockchain.\n📝 Original message:I don't see reason why not. It could just be another, longer, address type.\nThe advantage being that it allows for shorter transactions in the block\nchain (right?).\n\nWladimir\n\nOn Sat, Dec 17, 2011 at 7:32 AM, Luke-Jr \u003cluke at dashjr.org\u003e wrote:\n\n\u003e IMO, we should standardize and support public key addresses. While not\n\u003e ideal\n\u003e for humans, because of their length, it's a better fit for large QR Codes\n\u003e IMO.\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e Learn Windows Azure Live!  Tuesday, Dec 13, 2011\n\u003e Microsoft is holding a special Learn Windows Azure training event for\n\u003e developers. It will provide a great way to learn Windows Azure and what it\n\u003e provides. You can attend the event by watching it streamed LIVE online.\n\u003e Learn more at http://p.sf.net/sfu/ms-windowsazure\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20111217/f67c8cb3/attachment.html\u003e"}