From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mail.toke.dk; spf=pass (mailfrom) smtp.mailfrom=irif.fr (client-ip=2001:660:3301:8000::1:2; helo=korolev.univ-paris7.fr; envelope-from=jch@irif.fr; receiver=) Authentication-Results: mail.toke.dk; dkim=pass (2048-bit key; unprotected) header.d=irif.fr header.i=@irif.fr header.a=rsa-sha256 header.s=dkim-irif header.b=a20T5LtF Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) by mail.toke.dk (Postfix) with ESMTPS id 8676DA54C38 for ; Tue, 13 Feb 2024 14:14:46 +0100 (CET) Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/82085) with ESMTP id 41DDEj6L015762; Tue, 13 Feb 2024 14:14:45 +0100 Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 47D3AA9BD0; Tue, 13 Feb 2024 14:14:45 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=irif.fr; h= content-type:content-type:mime-version:user-agent:references :in-reply-to:subject:subject:from:from:message-id:date:date :received:received; s=dkim-irif; t=1707830083; x=1708694084; bh= W5GFSdIyLLnLd9xNw/qv6n0e5/VVkt2BOO49FKqRy2k=; b=a20T5LtFB+sSa44W IHsdFbVTyaVkze230q4Sejg/YWMwGk04CtU1oE43Ezuy20EFEwOvuWs7ZyhRMokm twmXRqtqRPvOuu4RgGUiYnXrob1fHDh4PdfX/3yybsuqBKSZjZZvJWtzsV0LzDoZ awkLBk8fSf/LBFrjjoYru+PEGrJp4Jcc3TpNwWO7biSgmfu/zU6oCvySeMu7B8zD dYRPqr0nLuqkXGuO4tYpAphRd2Q25vFt1H97ZNV7oMHFFWH+kNe94saMkHYJL7C1 1GQXU5gGQ/aW3uw89vWOC3yuVT+mz5JLkar2gGi8aXW/WOXJ7G+A+0TMODHuZRtm HlqzKQ== X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id nev7CMk-YFC4; Tue, 13 Feb 2024 14:14:43 +0100 (CET) Received: from pirx.irif.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id A1B05A9D8B; Tue, 13 Feb 2024 14:14:41 +0100 (CET) Date: Tue, 13 Feb 2024 14:14:41 +0100 Message-ID: <87o7ckecam.wl-jch@irif.fr> From: Juliusz Chroboczek To: Dirk-Willem van Gulik In-Reply-To: <9C5BACF6-2E9E-45E2-A3CB-619BB60DE670@webweaving.org> References: <9C5BACF6-2E9E-45E2-A3CB-619BB60DE670@webweaving.org> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/29.1 Mule/6.0 MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Tue, 13 Feb 2024 14:14:46 +0100 (CET) X-Miltered: at korolev with ID 65CB6B45.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 65CB6B45.002 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/ X-j-chkmail-Score: MSGID : 65CB6B45.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000 X-j-chkmail-Status: Ham Message-ID-Hash: WQIMJ64E5EE4OECEXBV6Q7AYDGO73GKA X-Message-ID-Hash: WQIMJ64E5EE4OECEXBV6Q7AYDGO73GKA X-MailFrom: jch@irif.fr X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: galene@lists.galene.org X-Mailman-Version: 3.3.9 Precedence: list Subject: [Galene] Re: Virtual groups v.s. new API branch List-Id: =?utf-8?q?Gal=C3=A8ne_videoconferencing_server_discussion_list?= Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: > to be able to have the /var/db/galene/groups directory (i.e. the -groups > cmd line argument) live on a nearby webserver. Basically it just fetches > the JSON remote every time. Right, makes sense. > The main reason for this is to allow the ad-hoc creation of short lived > ephemeral rooms that you discover you need, rather than > preconfigured. (the jsons are generated on the fly in typical 'cgi-bin' > conceptual fashion). 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. I'm not opposed to hosting group definitions on a remote server, but I'd need to understand why the existing mechanism does not meet your use case. > Now I just noticed this https://github.com/jech/galene/tree/api. Fair to > assume that this will be the `proper' way ? That's the plan, but it's still open to discussion. In order to create a group, you'll do: PUT /galene-api/group/groupname/ HTTP/1.1 If-None-Match: * Content-Type: application/json 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? > Or is there also a plan for a more 'reactive' mechanism -- i.e. one that > does not require a configuration sitting pretty `ahead' of time. We're > finding this quite useful (and then lock the room one we're started). I'm not opposed, but I'd need to understand why the "allow-subgroups" mechanism is not good enough for your use case. -- Juliusz