From: Juliusz Chroboczek <jch@irif.fr>
To: galene@lists.galene.org
Subject: [Galene] Should invites be enabled by default?
Date: Sun, 02 Apr 2023 20:03:58 +0200 [thread overview]
Message-ID: <87zg7qma9d.wl-jch@irif.fr> (raw)
Hi,
I'm just giving the finishing touches to the ablity to invite people to
a Galene group. In short, the user will click the invite button, and
Galene will generate a link of the form:
https://galene.org:8443/group/seminar/?token=XXXX
which can be used to autojoin a group. Unlike with the existing token
mechanism, the link will be revocable.
Whether this is allowed in a group will be configurable. However, should
it be enabled by default? In other words, should there be a configuration
directive
"allow-tokens": true
which enabled the functionality, or should there be instead a directive
"forbid-tokens": true
which enabled the functionality?
I'm very, very tempted to enable it by default for all users: it seems to
me that the ability to create tokens is better than having users share
passwords, and, since tokens are revokable, it doesn't remove any control
from the group operator. Do people agree?
-- Juliusz
reply other threads:[~2023-04-02 18:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87zg7qma9d.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=galene@lists.galene.org \
--subject='Re: [Galene] Should invites be enabled by default?' \
/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