đ
Original date posted:2015-02-05
đ Original message:Although not perfect, and it may require visual/verbal verification, I
don't see what the trust issue is.
[image: logo]
*Paul Puey* CEO / Co-Founder, Airbitz Inc
+1-619-850-8624 | http://airbitz.co | San Diego
<http://facebook.com/airbitz>; <http://twitter.com/airbitz>;
<https://plus.google.com/118173667510609425617>;
<https://go.airbitz.co/comments/feed/>; <http://linkedin.com/in/paulpuey>;
<https://angel.co/paul-puey>;
*DOWNLOAD THE AIRBITZ WALLET:*
<https://play.google.com/store/apps/details?id=com.airbitz>;
<https://itunes.apple.com/us/app/airbitz/id843536046>;
On Thu, Feb 5, 2015 at 2:05 PM, Eric Voskuil <eric at voskuil.org> wrote:
> Hi Paul,
>
> The issue is in the establishment of trust. Anyone can broadcast the
> initial information.
>
> e
>
> On Feb 5, 2015, at 2:01 PM, Paul Puey <paul at airbitz.co> wrote:
>
> The broadcast is ONLY done when the wallet is in Receive mode. Same as
> when the QR code is visible. The use of the *Name* section is specifically
> so that a recipient can broadcast their name/handle. Not so the recipient
> would broadcast the name of the Sender.
>
> On Thu, Feb 5, 2015 at 12:50 PM, Mike Hearn <mike at plan99.net> wrote:
>
>> I'm imagining myself walking around broadcasting my photo and MAC
>>> address while hucksters push payment requests to me for approval
>>
>>
>> I hate to break it to you, but you broadcast a photo of your face every
>> time you walk outside ;)
>>
>> Bluetooth MAC addresses are random, they aren't useful identifiers. If
>> someone can see you, a face is a far more uniquely identifying thing than a
>> MAC.
>>
>> "Payment spam" might be a problem. I can imagine a wallet requiring that
>> such requests are signed and then spammers can be blacklisted in the usual
>> fashion so they can't push things to your phone anymore. Anyway, a hurdle
>> that can be jumped if/when it becomes an issue.
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150205/1d6f9332/attachment.html>;
Paul Puey [ARCHIVE] /
npub1rjâŚ80ac2
2023-06-07 15:29:52
in reply to nevent1qâŚe3j7
Author Public Key
npub1rjuxg0r8xsxh36myahl6qvzrz2l8ku88cf2ghxej3a2g5wsdlmjq880ac2Seen on
wss://relay.nostr.bandPublished at
2023-06-07 15:29:52Event JSON
{
"id": "fdfdbe5d68d6674a738c7e6508374cb00f41833bf8c97b1388a0a61f63132d58",
"pubkey": "1cb8643c67340d78eb64edffa0304312be7b70e7c2548b9b328f548a3a0dfee4",
"created_at": 1686151792,
"kind": 1,
"tags": [
[
"e",
"5faa01afc6e1169d2a086249776b02fde5bfa851fa5197990b9cbcbf92c53f4a",
"",
"root"
],
[
"e",
"23e18b2b0d0187a60b5e3a26b85878e8812445d1444cb85aa598086ac8124c9a",
"",
"reply"
],
[
"p",
"82205f272f995d9be742779a3c19a2ae08522ca14824c3a3b01525fb5459161e"
]
],
"content": "đ
Original date posted:2015-02-05\nđ Original message:Although not perfect, and it may require visual/verbal verification, I\ndon't see what the trust issue is.\n\n\n[image: logo]\n*Paul Puey* CEO / Co-Founder, Airbitz Inc\n+1-619-850-8624 | http://airbitz.co | San Diego\n\u003chttp://facebook.com/airbitz\u003e \u003chttp://twitter.com/airbitz\u003e\n\u003chttps://plus.google.com/118173667510609425617\u003e\n\u003chttps://go.airbitz.co/comments/feed/\u003e \u003chttp://linkedin.com/in/paulpuey\u003e\n\u003chttps://angel.co/paul-puey\u003e\n*DOWNLOAD THE AIRBITZ WALLET:*\n \u003chttps://play.google.com/store/apps/details?id=com.airbitz\u003e\n\u003chttps://itunes.apple.com/us/app/airbitz/id843536046\u003e\n\n\n\n\nOn Thu, Feb 5, 2015 at 2:05 PM, Eric Voskuil \u003ceric at voskuil.org\u003e wrote:\n\n\u003e Hi Paul,\n\u003e\n\u003e The issue is in the establishment of trust. Anyone can broadcast the\n\u003e initial information.\n\u003e\n\u003e e\n\u003e\n\u003e On Feb 5, 2015, at 2:01 PM, Paul Puey \u003cpaul at airbitz.co\u003e wrote:\n\u003e\n\u003e The broadcast is ONLY done when the wallet is in Receive mode. Same as\n\u003e when the QR code is visible. The use of the *Name* section is specifically\n\u003e so that a recipient can broadcast their name/handle. Not so the recipient\n\u003e would broadcast the name of the Sender.\n\u003e\n\u003e On Thu, Feb 5, 2015 at 12:50 PM, Mike Hearn \u003cmike at plan99.net\u003e wrote:\n\u003e\n\u003e\u003e I'm imagining myself walking around broadcasting my photo and MAC\n\u003e\u003e\u003e address while hucksters push payment requests to me for approval\n\u003e\u003e\n\u003e\u003e\n\u003e\u003e I hate to break it to you, but you broadcast a photo of your face every\n\u003e\u003e time you walk outside ;)\n\u003e\u003e\n\u003e\u003e Bluetooth MAC addresses are random, they aren't useful identifiers. If\n\u003e\u003e someone can see you, a face is a far more uniquely identifying thing than a\n\u003e\u003e MAC.\n\u003e\u003e\n\u003e\u003e \"Payment spam\" might be a problem. I can imagine a wallet requiring that\n\u003e\u003e such requests are signed and then spammers can be blacklisted in the usual\n\u003e\u003e fashion so they can't push things to your phone anymore. Anyway, a hurdle\n\u003e\u003e that can be jumped if/when it becomes an issue.\n\u003e\u003e\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150205/1d6f9332/attachment.html\u003e",
"sig": "a190919db661fef92d3ead5fdcf5adfbc29fe0eb00c622c55f2478ef433ff84cfb679bf542c14b0569a14ff081bee34d33069c77f759fc86d4eec7bdeaf2b039"
}