Re: Proposed XMPP Extension: Payment Required
Tedd Sterr <[email protected]> Sat, 13 Jun 2026 17:56:21 +0000
| Newsgroups | gmane.network.jabber.standards-jig |
|---|---|
| Message-ID | <MA2P292MB0382BC223CD89B237CFCAB94AF192@MA2P292MB0382.ESPP292.PROD.OUTLOOK.COM> |
--===============4328616889772660517==
Content-Language: en-GB
Content-Type: multipart/alternative;
boundary="_000_MA2P292MB0382BC223CD89B237CFCAB94AF192MA2P292MB0382ESPP_"
--_000_MA2P292MB0382BC223CD89B237CFCAB94AF192MA2P292MB0382ESPP_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
> Perhaps we should just remove it, but then clients which don't know the U=
RI scheme won't be able to show the amount to the user, which sucks.
If a client can't display the amount because it doesn't understand the sche=
me, it's better to tell the user that explicitly ("Unknown payment scheme."=
) rather than some vague warning that the value might not be accurate, whil=
e still displaying the amount as if it's correct. And where the client does=
understand the scheme, that value is redundant and should be ignored by th=
e client anyway.
> Also, if we removed "display-amount", there's still a "label" field which=
could lie about the actual payment amount.
If we're going to have one potentially misleading value, let's go the whole=
way and have multiple? No.
It's possible the label could mention an amount, but it won't be displayed =
in the same way as the explicitly unknown transaction amount, and the sende=
r would have to expect the recipient doesn't have support for the scheme, o=
therwise the mismatch will be clear.
--_000_MA2P292MB0382BC223CD89B237CFCAB94AF192MA2P292MB0382ESPP_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div style=3D"margin-top: 0px; margin-bottom: 0px; font-family: "Arial=
", "Helvetica", sans-serif; font-size: 10pt; color: rgb(0, 0=
, 0);" class=3D"elementToProof">
> Perhaps we should just remove it, but then clients which don't know th=
e URI scheme won't be able to show the amount to the user, which sucks.</di=
v>
<div class=3D"elementToProof" style=3D"font-family: "Arial", &quo=
t;Helvetica", sans-serif; font-size: 10pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class=3D"elementToProof" style=3D"font-family: "Arial", &quo=
t;Helvetica", sans-serif; font-size: 10pt; color: rgb(0, 0, 0);">
If a client can't display the amount because it doesn't understand the sche=
me, it's better to tell the user that explicitly ("Unknown payment sch=
eme.") rather than some vague warning that the value might not be accu=
rate, while still displaying the amount as
if it's correct. And where the client does understand the scheme, that val=
ue is redundant and should be ignored by the client anyway.</div>
<div class=3D"elementToProof" style=3D"font-family: "Arial", &quo=
t;Helvetica", sans-serif; font-size: 10pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class=3D"elementToProof" style=3D"font-family: "Arial", &quo=
t;Helvetica", sans-serif; font-size: 10pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class=3D"elementToProof" style=3D"font-family: "Arial", &quo=
t;Helvetica", sans-serif; font-size: 10pt;">
<span style=3D"color: rgb(0, 0, 0);">> </span><span style=3D"color: rgb(=
0, 0, 0);">Also, if we removed "display-amount", there's still a =
"label" field which could lie about the actual payment amount.</s=
pan></div>
<div class=3D"elementToProof" style=3D"font-family: "Arial", &quo=
t;Helvetica", sans-serif; font-size: 10pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class=3D"elementToProof" style=3D"font-family: "Arial", &quo=
t;Helvetica", sans-serif; font-size: 10pt; color: rgb(0, 0, 0);">
If we're going to have one potentially misleading value, let's go the =
whole way and have multiple? No.</div>
<div class=3D"elementToProof" style=3D"font-family: "Arial", &quo=
t;Helvetica", sans-serif; font-size: 10pt; color: rgb(0, 0, 0);">
It's possible the label could mention an amount, but it won't be displayed =
in the same way as the explicitly unknown transaction amount, and the sende=
r would have to expect the recipient doesn't have support for the scheme, o=
therwise the mismatch will be clear.</div>
<div class=3D"elementToProof" style=3D"font-family: "Arial", &quo=
t;Helvetica", sans-serif; font-size: 10pt; color: rgb(0, 0, 0);">
<br>
</div>
</body>
</html>
--_000_MA2P292MB0382BC223CD89B237CFCAB94AF192MA2P292MB0382ESPP_--
--===============4328616889772660517==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Standards mailing list -- [email protected]
To unsubscribe send an email to [email protected]
--===============4328616889772660517==--