Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@irif.fr>
To: Dirk-Willem van Gulik <dirkx@webweaving.org>
Cc: galene@lists.galene.org
Subject: [Galene] Re: Virtual groups v.s. new API branch
Date: Tue, 13 Feb 2024 16:15:58 +0100	[thread overview]
Message-ID: <87mss4e6oh.wl-jch@irif.fr> (raw)
In-Reply-To: <D21B4C71-8D23-4CA7-923B-FA628C620C66@webweaving.org>

>> We use the "allow-subgroups" mechanism for that.  We create a template
>> group with "allow-subgroups" set to true, and subgroups are created on the
>> fly when a user joins.

> That sort of works - but we ended up (perhaps shooting ourselves in the
> foot) by also configuring auth, presenters, if it could, or could not,
> get recorded, etc.

I see.

>> with the group definition in the body.  Perhaps it's worth adding
>> "not-before" and "expires" fields to the group definition, and have groups
>> be automatically purged by the server?

> Not too worried about that - very easy to do with a DELETE from the
> configuration service once every night or so.

Ok.

> So conceivably - the API with subgroups may works if you accept that you
> get no 'callback' from Galene telling you that a new group was created
> (and we set them to private - so no polling of the public-public.json).

If you have an auth token, you can check if a group exists simply by doing
HEAD to /galene-api/group/whatever/.  No objection to implementing
a callback, though, if for some reason you cannot poll the server.

-- Juliusz

  reply	other threads:[~2024-02-13 15:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13  9:20 [Galene] " Dirk-Willem van Gulik
2024-02-13 13:14 ` [Galene] " Juliusz Chroboczek
2024-02-13 13:55   ` Dirk-Willem van Gulik
2024-02-13 15:15     ` Juliusz Chroboczek [this message]
2024-03-03 16:07     ` Juliusz Chroboczek

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=87mss4e6oh.wl-jch@irif.fr \
    --to=jch@irif.fr \
    --cc=dirkx@webweaving.org \
    --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