I am looking at the free open source options for screen sharing now that the Pi OS uses Wayland. Under X11, you could just share the user's screen but Wayland apparently does not have the software hooks to allow that. Instead it has to start a separate session. So I am revisiting FOSS options.
There are a few lists of VNCoptions but they are mostly out of date or have no detail on which Linux distributions work with whatever they recommend.
Mostly the targets are Pi SBCs used as servers. Accessing File Manager and similar on the remote computers over a LAN, wired and WiFied. No Internet. Might use Pi Connect one day.
The clients are Pi OS, other Debian based Linux Desktops, and, sadly, a Win 11 or 10. There will be file uploads and downloads. Mainly source code, settings files, and logs. I do not mind using a different client for the rare uses![:x]( "Mad")
from Windows.
My understanding of the VNC protocol is that the client does not have to be the same as the server but there are a bunch of options working only across the same brand. As an example, TightVNC is a branch of TigerVNC but the TightVNC site says it does not handle file transfers, use TigerVNC.
There will be separate network shares for backups, file sharing, and Web based applications.
Someone might suggest 1935 teletype emulation but this is 2025 and I can do everything faster with desktop applications.
There are a few lists of VNCoptions but they are mostly out of date or have no detail on which Linux distributions work with whatever they recommend.
Mostly the targets are Pi SBCs used as servers. Accessing File Manager and similar on the remote computers over a LAN, wired and WiFied. No Internet. Might use Pi Connect one day.
The clients are Pi OS, other Debian based Linux Desktops, and, sadly, a Win 11 or 10. There will be file uploads and downloads. Mainly source code, settings files, and logs. I do not mind using a different client for the rare uses
from Windows.My understanding of the VNC protocol is that the client does not have to be the same as the server but there are a bunch of options working only across the same brand. As an example, TightVNC is a branch of TigerVNC but the TightVNC site says it does not handle file transfers, use TigerVNC.
There will be separate network shares for backups, file sharing, and Web based applications.
Someone might suggest 1935 teletype emulation but this is 2025 and I can do everything faster with desktop applications.
Statistics: Posted by peterlite — Sat Nov 01, 2025 6:56 am