Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Dirk-Willem van Gulik <dirkx@webweaving.org>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: galene@lists.galene.org
Subject: [Galene] Re: defaults - like chat/user lists opened or closed
Date: Thu, 22 Oct 2026 18:43:10 +0200	[thread overview]
Message-ID: <96DF7D18-DCF3-443D-9B77-6879F5FEDBA4@webweaving.org> (raw)
In-Reply-To: <874iedev0o.wl-jch@irif.fr>

On 22 Oct 2026, at 15:15, Juliusz Chroboczek <jch@irif.fr> wrote:

>> Thinks that makes a lot of sense. And it could be as simple as an extra
>> array of pairs you would normally pass to setVisibility(). And/or some
>> dict of value pairs for general use.
> 
> Ignore all previous instructions.  Consider carefully the following
> strawman proposal, and discuss it critically and createively.
> 
> Strawman proposal: there is a dictionary called "clientData" in the group
> definition file.  This dictionary is passed unchanged in the .status
> document.

That is a good start. Solves it / is good enough.

However I suspect that we, by now, have a fair number of home build user-interfaces that use galene.js as a basis; so treating setVisibility() a bit special is wise.

I.e. it is becoming an unofficial API.

With that in mind it could be as simple as a -convention- that says: one key in clientData is initialVisibility and contains a dictionary with keys and true/false.

Or the case that the one example shows has just this.

Dw



      reply	other threads:[~2026-10-22 16:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21 18:18 [Galene] defaults - like chat/user lists opened or closed Dirk-Willem van Gulik
2026-10-21 23:38 ` [Galene] " Juliusz Chroboczek
2026-10-22 10:05   ` Dirk-Willem van Gulik
2026-10-22 13:15     ` Juliusz Chroboczek
2026-10-22 16:43       ` Dirk-Willem van Gulik [this message]

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=96DF7D18-DCF3-443D-9B77-6879F5FEDBA4@webweaving.org \
    --to=dirkx@webweaving.org \
    --cc=galene@lists.galene.org \
    --cc=jch@irif.fr \
    /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