{"type":"rich","version":"1.0","author_name":"npub14jv7tj33yt72yk8mljmvkck3p4xm5s3mxfpj289up38qqsn9dhkqeh00t4","author_url":"https://nostr.ae/npub14jv7tj33yt72yk8mljmvkck3p4xm5s3mxfpj289up38qqsn9dhkqeh00t4","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-03-23\n📝 Original message:I know that general approach to interaction design in Bitcoin assumes\nminimal to no difference between payer and payee, and generally I agree\nwith this approach.\nHowever, for the sake of my PoS development this assumption is wrong by\ndefault, as PoS is a specialized hardware, and one who cared to buy and\ninstall it is probably not in the same situation as the other party that\ndidn't care to by anything dedicated.\n\nIn short - from PoS point of view there is a customer and a merchant. And\nmy goal is to make thing work in assumption of fast and reliable connection\non merchant side and no connection requirement at all from customer side.\n\nI didn't put a silly example, as of my experience there are really a lot of\nplaces where cellphone connection isn't good enough for reliable Bitcoin\noperation. However, if we're talking about merchant establishments - we can\nhope for private local WiFi or wired connection on PoS side, so PoS\ninternet connection shouldn't be an issue. So this is the use case I'm\ndesigning around and this is why bluetooth based BIP70 implementation is\nimportant for me.\n\nI partly agree with Mike on user interface and IOU idea, but I have no\nintention to implement anything like that right now.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140323/de4912b2/attachment.html\u003e"}