Clipboard chaos with GFN desktop app

1. It’s well known that GFN compromises clipboard functionality. I tried contacting support but no solution was even attempted (their standard procedure is using third-party tools to in essence mitigate the problem they themselves create) - not a huge issue for me until here

2. GFN on itself makes the use of such alternative resources very inconvenient - a) the web tool from Steam overlay requires fresh logins every time it is used (which can be quite annoying depending on the security level of the user) + it brings substantial lag even for text use; b) the extremely useful and specific tool Notes also from Steam overlay becomes unusable - for some reason, it actually performs better than other alternatives in terms of % of success in the use of ctr c + ctr v, but GFN completely hinders its cloud syncing (which tends to work flawlessly in native Steam) - no absurd issue until here; but when you experience these limitations 25-30 times in a short time frame, yes it’s inconvenient to engage with (specifically when you are aware that those are tools that work smoothly outside of GFN)

3. GFN negative implications are not restricted to points 1 and 2 - I have experienced many times when the functionality of clipboard remains compromised AFTER the gaming session. If they happened exclusively when there’s a live launch, it’s bad of course but well I understand this is happening because of a huge and complex process that provides high performing game cloud streaming with no apparent lag. Once these issues take place when there’s no live session and happen even when the app is completely shut down, well this systemic / cross-domain problem get to the point of unacceptable - combining points 1, 2 and 3 makes the whole experience quite problematic, especially because there isn’t much action the user can take, as bypassing this intercept that GFN executes via Windows API Low-Level Keyboard Hook is realistic mainly using a browser to launch the service - which than has it own restrictions for users under the Performance Plan that really wouldn’t make sense as a practical compromise.

Yes yes AtlGr or Ctr + Alt + C were all attempted and technically they might even work at the moment of command execution, but even if positive I assume that GFN instantly overrides them before use