[bisq-network/bisq] Add option to make trade 'reason' less obvious (#2869)

cd2357 notifications at github.com
Sun May 10 06:33:35 UTC 2020


I don't think much can be gained from such a change.

**Best case**, it keeps privacy relatively unchanged but uses up dev resources to implement, test and spend time deciding on all kinds of new edge-cases:
* include emojis or not? some bank UIs do not allow that, having payment with emojis would look suspciious
* what is a good min/max length? some bank UIs limit that, people might not be able to use the "payment reason" which Bisq assigns to their trade
* what is a good character set? allow special characters? if yes, which ones (for which languages)? again, some online banking UIs do not allow much flexibility there, and people might not be able to type them in
* etc

**Worst case**, it actually decreases privacy and could introduce more issues:
* what to do about payments to-from same non-English speaking country? like from a bank account in Italy to another one in Italy? if an account has many such payments (perhaps trading in a local community?), when it is clearly unusual for locals to use English descriptions, well that might look suspicious
* how about a family account (owned by both people) suddenly having transactions with "Hey missed you" as description?
* traders currently use the payment description to match payments to the trades with that ID, if the description starts becoming some new random string or expression ("Rent for this month" etc), it will be much harder for them to decide which payments match which trades, and could cause lots of new support cases + unfinished trades + trades ending up in mediation. Especially for traders who don't do just 1-2 trades per month, but several per day, or several per week.
* etc

As mentioned in https://github.com/bisq-network/bisq/pull/4249#issuecomment-626278366 I'd say the current approach is good enough.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/2869#issuecomment-626281390
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200509/430d7fcf/attachment.html>


More information about the bisq-github mailing list