From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mail.toke.dk; spf=pass (mailfrom) smtp.mailfrom=webweaving.org (client-ip=148.251.234.232; helo=weser.webweaving.org; envelope-from=dirkx@webweaving.org; receiver=) Authentication-Results: mail.toke.dk; dkim=pass (1024-bit key; unprotected) header.d=webweaving.org header.i=@webweaving.org header.a=rsa-sha256 header.s=shared header.b=EUXtc34A Received: from weser.webweaving.org (weser.webweaving.org [148.251.234.232]) by mail.toke.dk (Postfix) with ESMTPS id 5DB26A54B83 for ; Tue, 13 Feb 2024 10:23:14 +0100 (CET) Received: from smtpclient.apple (83-85-39-103.cable.dynamic.v4.ziggo.nl [83.85.39.103]) (authenticated bits=0) by weser.webweaving.org (8.17.1/8.17.1) with ESMTPSA id 41D9Kale061516 (version=TLSv1.2 cipher=ECDHE-ECDSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 13 Feb 2024 10:20:40 +0100 (CET) (envelope-from dirkx@webweaving.org) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=webweaving.org; s=shared; t=1707816041; bh=a5S+IRUZaDVcDf6p1aDTIZcVg5gzJg33UWFUbMySaQo=; h=From:Subject:Date:To; b=EUXtc34A6fmzypSwmDWWWhHCiq8610dEOqkTmkHjaEb6px/zNXhSXUjUYVWNhDxwf 2qKWp1F1UjP63OIQzOqz/6IklTDhy7WIjws4v+k6YymF9xLV8Fg1Il6zvYSHNm2gq6 lYCYLWID0KAbjbZPNVOoAO+9fYtN+M7xrH5dRInE= X-Authentication-Warning: weser.webweaving.org: Host 83-85-39-103.cable.dynamic.v4.ziggo.nl [83.85.39.103] claimed to be smtpclient.apple From: Dirk-Willem van Gulik Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.300.61.1.2\)) Message-Id: <9C5BACF6-2E9E-45E2-A3CB-619BB60DE670@webweaving.org> Date: Tue, 13 Feb 2024 10:20:36 +0100 To: galene@lists.galene.org X-Mailer: Apple Mail (2.3774.300.61.1.2) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.4 (weser.webweaving.org [148.251.234.232]); Tue, 13 Feb 2024 10:20:41 +0100 (CET) Message-ID-Hash: 4YSL74LN572ONK4ES6TFX6V3KGX5QMOG X-Message-ID-Hash: 4YSL74LN572ONK4ES6TFX6V3KGX5QMOG X-MailFrom: dirkx@webweaving.org 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 X-Mailman-Version: 3.3.9 Precedence: list Subject: [Galene] 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: I've been using a bit of a hack in=20 group/Update) = https://github.com/jech/galene/blob/0f53bf037368a2a82a0af30ffd07bf5943b0ab= b1/group/group.go#L1335 and especially group/GetDescription() = https://github.com/jech/galene/blob/0f53bf037368a2a82a0af30ffd07bf5943b0ab= b1/group/group.go#L1007 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.=20 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). And this http/rev-proxy separation also makes it easier to limit the = access galene has; much like the galene-ldap separation/pattern. Now I just noticed this https://github.com/jech/galene/tree/api. Fair to = assume that this will be the `proper' way ?=20 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). With kind regards, Dw