> While VNC is in the name, KasmVNC differs from other VNC variants such as TigerVNC, RealVNC, and TurboVNC. KasmVNC has broken from the RFB specification which defines VNC, in order to support modern technologies and increase security.

I understand the reason why you'd want to break away from the spec, but why call it VNC then?

Do you know a different term that conveys the same idea and is similarly short?

Remote Desktop Software [1] [2] or Virtual Desktop Infrastructure [3]. Rfb is the protocol used by VNC, btw.

[1] https://en.wikipedia.org/wiki/Remote_desktop_software

[2] https://en.wikipedia.org/wiki/Comparison_of_remote_desktop_s...

[3] https://en.wikipedia.org/wiki/Desktop_virtualization#Remote_...

Yeah that’s equally short.

The Kasm docker containers are very cool. It's all on GitHub, too.

Just curiously, what's the name "Kasm" come from?

Remote Desktop {Tool,Technology}: RDT

see also https://news.ycombinator.com/item?id=39874356

While I agree using 'VNC' is a little questionable, I do think their use case together with graphical docker containers is rather cool: https://github.com/kasmtech/workspaces-images

I've been trying this out on a bunch of different servers and I find it to be quicker and more convenient than ordinary VNC. However, I couldn't find a version to put on OEL/Redhat 7 which is annoying.

By which I succinctly implied: does it support modern compositors (not just X), so that it can be used with most recent desktops. It IS perhaps the most important question in the space right now. VNC works with X only.

Another RMM to block for security <3