Pop-up and docs give contradictory advice on trade-id as reason for payment

[bitcoinwakanda]

Description

There are contradictory statements between the trading rules in the docs (https://docs.bisq.network/trading-rules) and the pop-up that appears in the app when making a trade. In the Bisq app it is recommended to NOT give the trade-id as the reason for payment, while in the docs are explicitly asking the users to enter the trade-id as reason for payment. Which one is the right behavior?

Version

v1.9.4

Steps to reproduce

Open a trade with SEPA payment and the notification appears.

Expected behaviour

The recommended behavior should be the same everywhere.

Actual behaviour

The recommended behavior is contradictory.

Screenshots

Bisq:

Docs:

Device or machine

Any

[boring-cyborg[bot]]

Thanks for opening your first issue here!

Be sure to follow the issue template. Your issue will be reviewed by a maintainer and labeled for further action.

[jmacxx]

Bisq app and Wiki are correct, the docs are outdated. Someone is going to correct it. Thankyou for reminding us.

@m52go @pazza83

[pazza83]

Hi @bitcoinwakanda thanks for raising this.

I think the whole https://docs.bisq.network/ should be retired.

It ranks well in search engines so maybe a 401 redirect should be used on each page to point to the corresponding wiki page. This way hopefully most of the search rankings will be transferred to the wiki.

[bitcoinwakanda]

Hi @bitcoinwakanda thanks for raising this.

I think the whole https://docs.bisq.network/ should be retired.

It ranks well in search engines so maybe a 401 redirect should be used on each page to point to the corresponding wiki page. This way hopefully most of the search rankings will be transferred to the wiki.

Makes sense, I also found it through a search engine.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant.