Pre-build custom RS_PUB_KEY & RENDEZVOUS_SERVER in github secrets still broken

Hi everyone, since my discussion in the Github repo was immediately closed, which is hilarious given the nature of this post, I'll try here.

I've been following this issue for over a year, and I've noticed that requests for this particular function are often closed without much explanation. I'm hoping we can have a productive discussion about this.

Previously, a workaround involved modifying RENDEZVOUS_SERVER and PUBLIC_RS_PUB_KEY in /libs/hbb_common/src/config.rs. However, since version 1.3.7, 'hbb_common' is now hard-linked to a new repository, making this approach more challenging.

I'm curious about the project's direction, particularly regarding the self-hosting aspect mentioned in the description: "An open-source remote desktop application designed for self-hosting, as an alternative to TeamViewer." It seems that recent changes might be shifting away from this focus.

I've also noticed some confusion in the community about contributions. Most of the posts on the discussion forum and in the issues I've read say, if anything, “please go ahead with your contribution.” or “fix it then.”. Why is that? There's a comment suggesting, "Try to fix it then, we don't use it, and this feature is added by a contributor." (https://github.com/rustdesk/rustdesk/issues/3328#issuecomment-1439628138). This raises questions about the acceptance and maintenance of community contributions. I mean, someone accepted the pull request for this feature at some point, now this it's clearly broken since ~2 years.

Regarding my use case: I use the application infrequently, perhaps 2-3 times a year, often for quick customer support. Mostly I just want to send the customer a download link from my fork and connect quickly without first explaining to the customer that he must enter some server adress and key. In some instances, I work in environments with strict security protocols that prohibit the use of remote desktop software over non protected servers. For these situations, I need a client that connects exclusively to my server over VPN. There is also the issue, that it is not possible for a non-root user on linux to change the network settings.

I'm interested in understanding the developers' perspective on this feature request. How can we work together to address this need while aligning with the project's goals? I'm open to suggestions and would appreciate any insights from the community and maintainers. But I'm also not a developer who can provide the solution myself.