Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Curtis Villamizar <curtis@orleans.occnc.com>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: Valent Turkovi? <valent@meshpointone.com>, galene@lists.galene.org
Subject: [Galene] Re: Gal?ne for bigger meeting (10-15 people) - problems and UX questions
Date: Sun, 19 Jul 2026 15:45:24 -0400	[thread overview]
Message-ID: <2841.1784490324@harbor5.andover.occnc.com> (raw)
In-Reply-To: Your message of "Thu, 16 Jul 2026 21:38:03 +0200." <87bjc6zpwk.wl-jch@irif.fr>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 1787 bytes --]

In message <87bjc6zpwk.wl-jch@irif.fr>
Juliusz Chroboczek writes:
> 
> > My feeling is there is quite a lot of UI/UX problems here. For example, by
> > default it asks "what you want - microphone, or microphone + camera". My guess
> > is that many people who had problems did not understand what this means, and
> > they left it on default "none", and that is why their audio did not work.
>  
> That's a deliberate design choice.  It is my opinion that a normal human
> being do not want to walk into a meeting with their camera switched on:
> they want to lurk for a while before they switch their camera on.  At
> least, that's my experience with students.
>  
> After a lot of discussions, I have agreed to add the login menu for those
> people who really want to show their face straight away, but the expected
> UX is that you come in, lurk for a while, then hit « Present ».
>  
> > I don't really understand why someone would log in to a room as chat only.
>  
> Because you want to listen to the discussion for a while before you
> participate?  Or perhaps because it's a lecture and you're a student who
> will only turn on their camera when they have a question to ask?
>  
> > Let the camera and microphone be off by default, but the browser must
> > have the permissions, because otherwise for a big number of people
> > Galène is useless - it will make problems and they simply will not use it.
>  
> I'm not sure.  Should we be asking for permissions even for those users
> who only intend to listen to the lecture?


The default could be set in the group definition.  chat-only for
lecture, camera+microphone for chat or meeting.  This way the person
setting up the group can make the decision based on how the group is
used.

Curtis

  reply	other threads:[~2026-07-19 23:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-16 14:19 [Galene] Galène for bigger meeting (10-15 people) - problems and UX questions Valent Turković
2026-07-16 16:28 ` [Galene] " Tim Panton
2026-07-16 17:24 ` err404
2026-07-16 19:38 ` Juliusz Chroboczek
2026-07-19 19:45   ` Curtis Villamizar [this message]
     [not found]   ` <178450473448.1644.1354246601774709853@gauss>
2026-07-20 10:14     ` [Galene] Re: Gal?ne " Juliusz Chroboczek
2026-07-20 14:37       ` Valent@MeshPoint
2026-07-20 16:03         ` 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=2841.1784490324@harbor5.andover.occnc.com \
    --to=curtis@orleans.occnc.com \
    --cc=galene@lists.galene.org \
    --cc=jch@irif.fr \
    --cc=valent@meshpointone.com \
    /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