monero-patches VS monero-gui

This time I saw no need of opening any branches in Monero Core/GUI. I only focused on maintaining the already opened branches and trying to get them merged. However due to negative propaganda towards my work, it was so far impossible to do it and I spent a good deal of time on trying to prove my points. So far to no avail. See the recently updated (very technical) report under this PR. An outline of this entire discussion would be that: - it was being misunderstood all the time (for 2 years now?), that my speed improvements were targeted for developers, who are supposed to compile the code very often and very quickly, rather than users, who would compile the code from source only once in a quarter. - as such, even though I provided objective methods of measurements (the Clang Build Time Analyser script), their results were being doubted all the time and confronted with measurements done from the User's perspective. In case of 7217, these measurements were underestimating my measurements greatly. - I had to create special tooling here & here, that executes the appropriate build time tests on GitHub's servers, where nobody can tamper the results in neither of the two directions.

If you just misspell one word of 25 the check word won't be right and there should be an error message. Any random set of seed words (with the correct check word) will be a valid wallet address, however accidentally getting a valid check word is unlikely. If you are not using 25 seed words this issue might be relevant: https://github.com/monero-project/monero-gui/issues/1326

It's not a virus: https://github.com/monero-project/monero-gui/issues/3708

I'd probably start at the Monero GUI Wallet: https://github.com/monero-project/monero-gui

GUI has P2Pool/XMRig support as seen here

The PR for portable mode says:

See: https://github.com/monero-project/monero-gui/issues/4087