From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mail.toke.dk; dkim=pass header.d=orleans.occnc.com header.i=@orleans.occnc.com header.a=rsa-sha256 header.s=curtis-orleans-20260328-122414 header.b=KryUj9xq; arc=none (Message is not ARC signed); dmarc=pass (Used From Domain Record) header.from=orleans.occnc.com policy.dmarc=none Received: from mta5-tap0.andover.occnc.com (mta5-tap0.andover.occnc.com [IPv6:2600:2c00:b000:2500::151]) by mail.toke.dk (Postfix) with ESMTPS id 388FC13665F5 for ; Mon, 20 Jul 2026 01:45:31 +0200 (CEST) Received: from harbor5.andover.occnc.com (harbor5.andover.occnc.com [IPv6:2600:2c00:b000:2500::510b]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519MLKEM768 server-signature ECDSA (secp384r1) server-digest SHA384) (Client did not present a certificate) (Authenticated sender: curtis@occnc.com) by mta5-tap0.andover.occnc.com (Postfix) with ESMTPSA id 98ED4D77A; Sun, 19 Jul 2026 19:45:27 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=orleans.occnc.com; s=curtis-orleans-20260328-122414; t=1784504727; bh=5rr60aUxFI5JKEdU1CPhM8n3THnDYdYEvifvGCxwuGU=; h=To:cc:Reply-To:From:Subject:In-reply-to:Date; b=KryUj9xqfPAQzCQ7vGNr3EYMu5ZaBHfZDytxl52YPqQ3F7bFwUmtfSjuaWzCUKwEk 9XCsgJ3IvOvZ0ppx8qF7LX8gm51uu2gZtDzSXheR0xFEjnrmx2INUBIpjtOkhGIdKu 74Fkr6Uf0GcCbjOAMVs0sHX5XVMIE41IKO5uVd5bdlVPTE7IQp6MCSF/ROR5Z7xMV7 jGihdlbFYuJ01zl6WM+ro5k/PWExSGx2qGWiqJwQM7W6rgxYUqyNFYxlUoZWa2s/oT bx/W9pvtanjVbUn/Jx/sLTEXHteC1kTWwtLBSJqAL0MppYdvTZtQWaKula7uCYbHyI j+DlVf5DGvWow== To: Juliusz Chroboczek cc: Valent Turkovi? , galene@lists.galene.org From: Curtis Villamizar In-reply-to: Your message of "Thu, 16 Jul 2026 21:38:03 +0200." <87bjc6zpwk.wl-jch@irif.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <2840.1784490324.1@harbor5.andover.occnc.com> Content-Transfer-Encoding: quoted-printable Date: Sun, 19 Jul 2026 15:45:24 -0400 Message-ID: <2841.1784490324@harbor5.andover.occnc.com> Message-ID-Hash: JN5WVKWTNB65AJHY7BZHHJADWHNTFBD5 X-Message-ID-Hash: JN5WVKWTNB65AJHY7BZHHJADWHNTFBD5 X-MailFrom: curtis@orleans.occnc.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list Reply-To: Curtis Villamizar Subject: [Galene] Re: Gal?ne for bigger meeting (10-15 people) - problems and UX questions 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: 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 mean= s, and > > they left it on default "none", and that is why their audio did not wo= rk. > = > 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 thos= e > people who really want to show their face straight away, but the expecte= d > UX is that you come in, lurk for a while, then hit =AB Present =BB. > = > > I don't really understand why someone would log in to a room as chat o= nly. > = > 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=E8ne is useless - it will make problems and they simply will not u= se 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