The Cutting Room Floor - CollabVM Server
CollabVM Server is everyone's favorite server that powers CollabVM. This article covers CollabVM Server 1, and will cover CollabVM Server 2 upon its release, assuming there are any cut features found.
At one point, CollabVM Server 1.x had different username colors which indicated ranks. Red indicated an administrator, blue indicated a developer, and black indicated a registered user. These roles were never finished and mostly don't work properly.
While the red administrator role was cut, it can be reactivated through this patch. This is no longer cut as of version 1.2.9, where it was officially added.
This feature was officially added into CollabVM Server 2.0.
There is a reference to a "RegisteredUser" role in the server, so there is some support in the server for it, although there is currently no way to activate it through normal means. It is rather difficult to distinguish a guest user from a normal user although if you look at it very closely, you can tell a user has a darker shade of black than a guest.
This suggests that at some point, guests were meant to have different colors than registered users.
It is worth noting that at one point, accounts were meant to be added into CollabVM Server 1.2, but this was cut and was added into CollabVM Server 2.0 instead.
Connect to Monitor
A "Connect to Monitor" button is present in the admin panel but is commented out. This was presumably used in a very early iteration of the Admin Panel as the panel automatically connects to the QEMU Monitor in newer versions.
Disable Change Username
Presumably would allow you to prevent username changing on the VM. No code for this function exists in the server.
Disable Virtual Keyboard
Presumably would allow you to prevent using the virtual Guacamole keyboard. No code for this function exists in the server.
Alongside "Restore on Shutdown", a feature to restore a VM periodically is present, but commented out in the source code. Code for this feature is also present in the server. It allowed you to automatically restore a VM every x amount of hours and x amount of minutes. This would have a similar function to socket.computer which restored every 15 minutes. This feature was never finished and does not work correctly.