If you are so keen on correctness, please don't say "LLMs are lying". Lying is a conscious action of deceiving. LLMs are not capable of that. That's exactly the problem: they don't think, they just assemble with probability. If they could lie, they could also produce real answers.
Yup, I don't understand it either. Many "how to fix ..." articles involve quite a lot powershell magic. And I say "magic" because IMO they are often essentially API calls which I find far harder to grasp than config files that follow some logic and help me understand what is interacting how.
They said "in addition to registry editing".
I said it's possible, just much more effort than the current solution which only requires reading and and parsing the process name on startup.
They still need to know the key. If you publicly distribute your config, that's a problem. But IMO one even the pro version couldn't solve.
If it's so easy to implement, go ahead and open a PR. The community will be thankful.
The apps are bundled completely differently on OSX and Linux. It's technically not possible to do the same thing there. Also this is not a free/paid limitation at all.
They could maybe build a packaging tool that can customize the binaries (adding data to the PE executable in Windows and maybe a property file in OSX and Linux); but that's quite some effort for not much gain.
They also document scripts to bootstrap clients on other OSses. And I don't think you need Pro to build rustdesk yourself - they even document the process.
You joke, but I actually have a license key for WinRAR that I use with the native rar cli on my Linux machines.
Buy CrossOver for Linux. Positive side effect: you support Wine development.
... yet.
What I find weird about Tumbleweed is, that updating is not integrated into YaST or another UI. You have to use the commandline to keep your system up to date. That makes it exactly as inconvenient as Arch for newcomers, but Arch has a whole philosophy behind this while SuSE is typically very GUI oriented. It's weird.