{"type":"rich","version":"1.0","author_name":"npub1sgs97fe0n9wehe6zw7drcxdz4cy9yt9pfqjv8gasz5jlk4zezc0quppx3c","author_url":"https://nostr.ae/npub1sgs97fe0n9wehe6zw7drcxdz4cy9yt9pfqjv8gasz5jlk4zezc0quppx3c","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-02-05\n📝 Original message:On 02/05/2015 12:50 PM, Mike Hearn wrote:\n\u003e     I'm imagining myself walking around broadcasting my photo and MAC\n\u003e     address while hucksters push payment requests to me for approval\n\u003e \n\u003e I hate to break it to you, but you broadcast a photo of your face every\n\u003e time you walk outside ;)\n\u003e \n\u003e Bluetooth MAC addresses are random, they aren't useful identifiers. If\n\u003e someone can see you, a face is a far more uniquely identifying thing\n\u003e than a MAC.\n\nInteresting take on privacy. But the market will of course decide.\n\nWould the merchant be broadcasting payment requests in the clear, or\nwould they be encrypted with a public key of the spender?\n\n\u003e \"Payment spam\" might be a problem. I can imagine a wallet requiring that\n\u003e such requests are signed and then spammers can be blacklisted in the\n\u003e usual fashion so they can't push things to your phone anymore. Anyway, a\n\u003e hurdle that can be jumped if/when it becomes an issue.\n\nNot sure I'd shoot for a system that's guaranteed to require PKI with\nblacklisting and spam filtering.\n\ne\n\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 473 bytes\nDesc: OpenPGP digital signature\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150205/d727f4f8/attachment.sig\u003e"}