Currently a user must have already opted to supervise before a user can start a session and add them as supervisor. If a user selects /supervise after a session has started the monitored user must select /begin again to add the supervisor. This is poor UX and puts an onus on the monitored user to manage their supervision.
It may be advantageous for users to be able to add themselves as supervisors to existing sessions. We could add a command /supervise_xxxxxx which would add the user to session xxxxxx. The list of sessions could be displayed with a command, e.g. /list_sessions with each session showing the monitored user's name and the /supervise_xxxxx command.
This feels like a reasonable solution but does raise the question about privacy and security. Currently anyone can be a monitored or supervised user.
Currently a user must have already opted to supervise before a user can start a session and add them as supervisor. If a user selects
/supervise
after a session has started the monitored user must select/begin
again to add the supervisor. This is poor UX and puts an onus on the monitored user to manage their supervision.It may be advantageous for users to be able to add themselves as supervisors to existing sessions. We could add a command
/supervise_xxxxxx
which would add the user to session xxxxxx. The list of sessions could be displayed with a command, e.g./list_sessions
with each session showing the monitored user's name and the/supervise_xxxxx
command.This feels like a reasonable solution but does raise the question about privacy and security. Currently anyone can be a monitored or supervised user.