From: "Michael Ströder" <michael@stroeder.com>
To: galene@lists.galene.org
Subject: [Galene] Re: autolock always locks
Date: Thu, 14 Jan 2021 18:40:28 +0100 [thread overview]
Message-ID: <26f253e5-a7ed-53dd-6c18-ec2c4228edd4@stroeder.com> (raw)
In-Reply-To: <87turj5spy.wl-jch@irif.fr>
On 1/14/21 6:33 PM, Juliusz Chroboczek wrote:
>> 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?
Yeah, our e-mails crossed.
Would it be possible to implement an ops inactivity timeout before all
attendees are kicked out? With this the ops would have a fair chance to
re-connect in time.
> What about adding a command "/kickall"
Would be useful. But what happens in case ops cannot reconnect due to
persistent issues?
Ciao, Michael.
next prev parent reply other threads:[~2021-01-14 17:40 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
2021-01-14 17:40 ` Michael Ströder [this message]
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=26f253e5-a7ed-53dd-6c18-ec2c4228edd4@stroeder.com \
--to=michael@stroeder.com \
--cc=galene@lists.galene.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox