📅 Original date posted:2014-03-06
📝 Original message:On 03/06/2014 02:44 PM, Mike Hearn wrote:
> I'm not sure if iso-dep is the way to go here. Afaik as soon as you pick
> up the phone the connection breaks.
>
> If the phone isn't willing to immediately authorise then it'd have to
> fall back to HTTPS or Bluetooth as normal.
Ok, that would be an option.
> Besides, how do you plan to risk-analyse the memo field?
>
> I guess only the amount and destination are relevant for risk analysis.
The memo field (and its logical evolution, an invoice) also needs to be
verified, since its part of the contract. Imagine sitting in a
restaurant and you're being presented the bill, most people will do a
quick scan of the meals and drinks consumed (and non-malignant errors
are frequent in that business).
> It's already very short if you can do without Android Beam, e.g. on
> Android 2.3.
>
> I think IsoDep based protocols must bypass Beam - when I scan my
> e-passport there's no beam animation.
Everything except Beam bypasses Beam (-: Beam is an Android-specific
protocol. I assume it would also be possible to write an own NDEF
implementation on top of the low level NFC APIs. I want to try as soon
as I have a second NFC-capable phone, preferably Android 4.4.
> Even the current ~10 second roundtrip is a huge improvement to the
> status quo. I recently tried to buy a subway ticket and it took me 7
> full minutes (just for the payment process)!
>
> Then that subway kind of sucks ;)
You can't really blame the subway for a broken payment process.
> Have you been to London and used Oyster?
Yes, it was a complete disaster. Obtaining a ticket took even longer --
ca. 45 minutes. Boarding the train took some additional seconds,
compared to no overhead in Germany where we simply don't have any gates.
On top of that, you walk more (in tunnels) than you get driven around,
get tracked on each movement and if you want to get your (monetary)
change, you need to wait for another 45 minutes.
The upside is, when going by public transport in England I always feel
like Mr. Freeman in City 17 (-:
Andreas Schildbach [ARCHIVE] /
npub1xg…adsv7
2023-06-07 15:14:50
in reply to nevent1q…p7pp
Author Public Key
npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7Published at
2023-06-07 15:14:50Event JSON
{
"id": "5e99fc4d2bce2685239971b789df2d9e352e05a6c94f6598462c65dc3f654051",
"pubkey": "3215b3d77dff1f84eeb5ad46fb1206a8d1657b3ea765a80b5489ece3a702d2bc",
"created_at": 1686150890,
"kind": 1,
"tags": [
[
"e",
"a596a87c6af457be0f805b03270c063d690d47775921aaf8262e434ce379245e",
"",
"root"
],
[
"e",
"92fde36acf349087f96cdef922e4a6bb837c09f9a36c38ecbed350d7a5454a0f",
"",
"reply"
],
[
"p",
"f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2"
]
],
"content": "📅 Original date posted:2014-03-06\n📝 Original message:On 03/06/2014 02:44 PM, Mike Hearn wrote:\n\n\u003e I'm not sure if iso-dep is the way to go here. Afaik as soon as you pick\n\u003e up the phone the connection breaks.\n\u003e \n\u003e If the phone isn't willing to immediately authorise then it'd have to\n\u003e fall back to HTTPS or Bluetooth as normal.\n\nOk, that would be an option.\n\n\u003e Besides, how do you plan to risk-analyse the memo field?\n\u003e \n\u003e I guess only the amount and destination are relevant for risk analysis.\n\nThe memo field (and its logical evolution, an invoice) also needs to be\nverified, since its part of the contract. Imagine sitting in a\nrestaurant and you're being presented the bill, most people will do a\nquick scan of the meals and drinks consumed (and non-malignant errors\nare frequent in that business).\n\n\u003e It's already very short if you can do without Android Beam, e.g. on\n\u003e Android 2.3.\n\u003e \n\u003e I think IsoDep based protocols must bypass Beam - when I scan my\n\u003e e-passport there's no beam animation.\n\nEverything except Beam bypasses Beam (-: Beam is an Android-specific\nprotocol. I assume it would also be possible to write an own NDEF\nimplementation on top of the low level NFC APIs. I want to try as soon\nas I have a second NFC-capable phone, preferably Android 4.4.\n\n\u003e Even the current ~10 second roundtrip is a huge improvement to the\n\u003e status quo. I recently tried to buy a subway ticket and it took me 7\n\u003e full minutes (just for the payment process)!\n\u003e \n\u003e Then that subway kind of sucks ;)\n\nYou can't really blame the subway for a broken payment process.\n\n\u003e Have you been to London and used Oyster?\n\nYes, it was a complete disaster. Obtaining a ticket took even longer --\nca. 45 minutes. Boarding the train took some additional seconds,\ncompared to no overhead in Germany where we simply don't have any gates.\n\nOn top of that, you walk more (in tunnels) than you get driven around,\nget tracked on each movement and if you want to get your (monetary)\nchange, you need to wait for another 45 minutes.\n\nThe upside is, when going by public transport in England I always feel\nlike Mr. Freeman in City 17 (-:",
"sig": "dfcf67ebe4775c778d3aa0b3d4e111a9cab3d52fa44c19d37dd167befb127cf5cc8f4bdcb6423121b1ee751efb6db42f3374a27fa0afa572a26bc165288ec67b"
}