summaryrefslogtreecommitdiff
path: root/stuff.txt
diff options
context:
space:
mode:
authorFlorian Dold <florian.dold@gmail.com>2018-10-10 22:58:50 +0200
committerFlorian Dold <florian.dold@gmail.com>2018-10-10 22:58:50 +0200
commitb1860c12fd3b654efcd0cbb397aa2cd07b16ef69 (patch)
tree24e3a3a17a5dd540bbdd22b7c151a1437ddd110a /stuff.txt
parent44e0d2f9fa4e5d4b6354a2cab324ecc87cfc90d3 (diff)
downloaddold-thesis-phd-b1860c12fd3b654efcd0cbb397aa2cd07b16ef69.tar.gz
dold-thesis-phd-b1860c12fd3b654efcd0cbb397aa2cd07b16ef69.tar.bz2
dold-thesis-phd-b1860c12fd3b654efcd0cbb397aa2cd07b16ef69.zip
sync
Diffstat (limited to 'stuff.txt')
-rw-r--r--stuff.txt15
1 files changed, 15 insertions, 0 deletions
diff --git a/stuff.txt b/stuff.txt
index 65c428e..3767746 100644
--- a/stuff.txt
+++ b/stuff.txt
@@ -29,6 +29,13 @@ Q&A:
where do we show how expensive refresh is in terms of the time needed?
+should the implementation chapter's related work moved to the general related
+work chapter?
+
+where should we explain the wire fee amortization?
+
+where do we define what "origin" means in a web context?
+
would it not be better if the exchange knew about the amount for a contract
and could refund automatically if the payment wasn't completed before the pay deadline?
=> No, since the customer can complete the payment themselves
@@ -40,6 +47,9 @@ Do we support in the implementation that different deposits are unlinkable
from the contract? It does not currently look like it, we mix both cases,
leading to some confusion.
+should we use headers instead of extended fulfillment URL?
+=> NO, for forward compat reasons, as well as privacy and simplicity
+
Should I have a notation index?
=> ?
@@ -92,6 +102,11 @@ Are practical anonymity concerns discussed properly (amounts, denomination, cont
--------------------------
+
+- the resource URL should *always* be specified
+ when paying for resources, as otherwise the fallback
+ to taler:pay does not work!
+
- NFC
- indian merchant scenario using KYC hash