[bisq-network/bisq] Revert "Deactive confirm buttons once mediation started" (#4562)

[chimp1984]

> But this is exactly my point: **Arbitration is a conflict resolution service; Mediation is just a help service.**
> 
> As a Mediator, I am merely a neutral third party who helps traders work out their issues so they can complete the trade between themselves. It is only after 10 or 20 days when my efforts to mediate are unsuccessful that Arbitration is required. Before this change, for about 80% of my mediation cases I never had to make a suggested payout, and could close with TRADE_ALREADY_SETTLED, because the mediation was either successful or unnecessary, and the traders were able to complete the trades themselves.

Thats great if they can settle themselfes, but of course mediation is also conflict resolution, otherwise there would not be the feature of the mediated payout suggestion. If one side breaks clearly the trade obligations the mediator has to apply some penalization, otherwise it's an invitation for traders to ignore the rules. I fear this aspect is not taken enough seriously by mediators as far I have seen some data (not in depth, but was my impression when responding to some reimbursement cases).
 
> But most of all, this UI tweak actually changes the way trading on Bisq works, and users are reporting it as a bug, which I agree with - there is no reason this button should be disabled. If your goal is to fix an actual security flaw in the trade protocol, please do it in trade protocol, and not in the GUI for security theater.

Lets not get into such a polemic discussion mode... I explained the details already why a trade protocol change would not be justified (would also come with backward compatibility challenges). 

As stated above I agree that we should improve it, but try to find an improvement which avoids the abuse from sellers, even if it is not a "security" feature but just makes it hard enough for 99.9% of traders to be able to keep abusing it, the goal for reducing cases where seller confirms in last moment is met.

-- 
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/pull/4562#issuecomment-699661983
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200927/4ed07b8a/attachment.html>