Regarding
https://github.com/nwjs/nw.js/issues/7970 . Yes, the reason for this post was Cloudflare's captcha. However, a Chromium build that reports the same data as NW,js including
navigator.userAgentData.brands passes the captcha. So Cloudflare is able to distinguish between NW.js and Chromium, not even Chrome, that reported exactly the same fingerprinting information according to https://amiunique.org/fp.
Also, if one just adds --user-agent="exact string as used by Firefox or Safary or a string like bla-bla-bla" to NW.js invocation, the capture can be passed. So it seems Cloudflare tries particularly hard to detect the real browser when the user agent and the related data tells it is Chrome or Chromium.
Regards, Igor