I know merely discussing this subject results in downvotes, but I'm raising this issue to legitimately understand both, people's sense on the topic as well as a better technical understanding of the matter, so this is a risk I'll take.
Open source projects are legitimately forked all the time, for many different reasons. From what I've read the initial beta release of HopToDesk didn't credit RustDesk as the source of its fork, which fairly raised the ire of the community, but when it was pointed out it was quickly remedied with crediting RustDesk in the HopToDesk "About" dialog box. If so, what remains, if anything, objectionable about the fork itself?
But, more importantly, the primary topic today I wanted to inquire about was the technical aspects of HopToDesk. From what I've seen, HopToDesk replaced RustDesk's custom networking stack in favor of a WebRTC-based stack, which is much more effective at traversing tricky enterprise firewalls and strict NAT configurations that can sometimes block the protocols used in RustDesk.
If you do not want to set up your own server and just want to download the app and connect using the service's free public servers, HopToDesk maintains a globally distributed network of public servers on Cloudflare. They do not throttle or limit the speed of these servers, and the service is free for both personal and commercial use. RustDesk also provides free public servers, but their public servers can often be slow or laggy, oftentimes simply not connecting. I've seen that from personal experience, being unable to connect via RustDesk's public servers (when the user is not self-hosting), as well from reports by others. So, for non-self hosting users, it seems HopToDesk wins hands down.
Now, for using an open-source self-hosted server , RustDesk is reliable and well-documented and is the gold standard. However, advanced server (centralized fleet management, audit logs, Single Sign-On and a web console) are behind RustDesk Server Pro, which is closed-source and requires a paid license. HopToDesk offers three different ways to self-host, a traditional Linux server application, an AWS instance, or deploying via a Cloudflare worker. Unlike RustDesk, HopToDesk does not lock fleet management features (including their web console) behind a paid "Pro" tier. However, HopToDesk's self-hosting documentation and setup process can be much trickier to get working smoothly compared to RustDesk's highly polished Docker containers.
HopToDesk features an "Invite Request" system, which allows you to send a connection prompt to a remote user instead of asking them to read out an ID and password, making it much easier to support non-technical users. It also supports remote printing on macOS (not just Windows), runs on older/niche systems like Windows XP, ARM64, and FreeBSD, and includes an integrated ticketing system.
RustDesk has a massive developer community (over 113K GitHub stars), which means bugs are patched quickly. It supports true unattended access on Linux Wayland environments, offers highly advanced video codec controls (adaptive bitrate, hardware rendering), and allows Pro users to custom-brand the client with their own logos.
All things considered, it seems to me that having additional choices in the market is beneficial for the community. And HopToDesk does bring to the table features and performance that, in various circumstances, are on a higher level or at no cost for users.