Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@irif.fr>
To: "Michael Ströder" <michael@stroeder.com>
Cc: galene@lists.galene.org
Subject: [Galene] Re: autolock always locks
Date: Thu, 14 Jan 2021 18:33:13 +0100	[thread overview]
Message-ID: <87turj5spy.wl-jch@irif.fr> (raw)
In-Reply-To: <7af360d1-0449-a011-0d99-fd2100c03a7e@stroeder.com>

> But compared to privacy issues I'm much more frightened of someone
> abusing my unattended Galène installation for something really bad

[...]

> So IMO an autokick option would not only be featuritis.

What happens if the operator gets disconnected, for example because he
closed the wrong navigator tab or because he moved from WiFi to 4G which
broke the websocket?  When he comes back, everyone has been kicked out.
(Obviously, we cannot detect if the op has closed the tab by mistake or
deliberately.)

What about adding a command "/kickall" that kicks everyone out (including
operators)?  So at the end of a meeting the operator can say

  /kickall
  /lock

and if he forgets, autolock will kick in (no pun intended) but users won't
be automatically kicked out.

-- Juliusz

  parent reply	other threads:[~2021-01-14 17:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14  9:19 [Galene] " Michael Ströder
2021-01-14 12:36 ` [Galene] " Juliusz Chroboczek
2021-01-14 12:38   ` Gabriel Kerneis
2021-01-14 12:55     ` Juliusz Chroboczek
2021-01-14 12:58       ` Michael Ströder
2021-01-14 15:26         ` Juliusz Chroboczek
2021-01-14 15:41           ` Michael Ströder
2021-01-14 17:17             ` Toke Høiland-Jørgensen
2021-01-14 17:29               ` Michael Ströder
2021-01-14 17:33             ` Juliusz Chroboczek [this message]
2021-01-14 17:40               ` Michael Ströder
2021-01-17 20:30                 ` Juliusz Chroboczek
2021-01-14 12:56     ` Michael Ströder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87turj5spy.wl-jch@irif.fr \
    --to=jch@irif.fr \
    --cc=galene@lists.galene.org \
    --cc=michael@stroeder.com \
    --subject='[Galene] Re: autolock always locks' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox