Ah you got me I guess, didn't think of the VPN case. It does seem like an asterisk in the grand scheme, especially since the applicability of this tech in LANs

Ah you got me I guess, didn't think of the VPN case. It does seem like an asterisk in the grand scheme, especially since the applicability of this tech in LANs is very limited (there's no lag in LAN, and it's already internet in the sense that it uses IP, you would need to consider an ethernet framing tool or a unix socket tool like X11 for truly local-remote protocol), so this would only useful in this network-virtualized VPN ecosystem (and also in scenarios where you want to ensure no third party handles the data, by self hosting the server part of parsec) What is clear to me is that Parsec belongs to a newer breed of remote tools, inline with TeamViewer and AnyDesk, that primarily respond to the need of post ISP firewall era, where by default ports are blocked, so peerless remote tooling becomes harder to install and administer, these have a client-server-client based architecture. And Parsec builds upon this architecture by placing some secret lag reducing sauce on their Server instead of just authenticating and forwarding. My guess is that they have a proprietary predictive and interpolation based OS algorithm tightly coupled to the OS UI, and this secret sauce lives and is closed source on their backend, so you would kind of need to host a third server in the middle, maybe we will see a competitor for a VPN niche, or an open source alternative. If an open source solution arises, I bet that it would require an installation of a server, and it would probably start with X11 or Wayland tight coupling.