Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Jeroen <jeroen@garage44.org>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: "galene@lists.galene.org" <galene@lists.galene.org>
Subject: [Galene] Re: Pyrite update
Date: Mon, 03 Nov 2025 19:54:37 +0000	[thread overview]
Message-ID: <J4mx_gjsRvJNKtiyYXXlm06UyTKzTm-XwYvxbnrGuLiOXVUlnjiHxxZHgYw44DZSHpL2LUcqUroDB-Vo4bjXaAqBPBLMOxwLVLUPkZGq-ks=@garage44.org> (raw)
In-Reply-To: <87tszbpcog.wl-jch@irif.fr>

Op maandag 3 november 2025 om 12:40 PM schreef Juliusz Chroboczek <jch@irif.fr>:

> 
> 
> >> Hmm... will it still be usable for casual videoconferences?
> 
> > With casual, do you mean that it should be possible to join a video
> > conference without registering/using an account?
> 
> 
> Suppose we need to discuss something on Galene. I generate a token in an
> autogenerated subgroup, send it to you over SMS or e-mail, and we're
> chatting.
Alright; I hadn't thought this through yet :)
I suppose each channel/group could have an invite option to start with? Groups that are locked 
or for some other reason not accessible due to permissions, won't show the option off-course. 
Now this still depends on an admin managed channel layout, which is not very flexible.

> 
> Suppose we need to discuss something on Zulip. I need to setup a group,
> then I need to ask you to create an account, which fails because I set the
> wrong permissions on the group, at which point we call it a day and go
> drinking with our respective friends.

But, users also will have their own private channel (Direct messages) in this setup. It may be an idea to 
create a matching dedicated Galene group/subgroup (e.g. users/<user>) for each private channel, 
so if a user wants to have a quick video conference/chat, they then can use the invite option 
on that dedicated channel. In this setup, a user doesn't have to think about channel creation 
anymore, because channel-less conferences exists at a fixed place (in a channel :)). The same can 
probably be accomplished with a separate "Start conference" button, but then where should the info 
about this volatile channel be shown? 

After a conference session, the chat will still be there for historical purposes. I'm not really sure if 
the latter is desired behavior. It may be nice to have some form of grouping of chat messages per conference 
and actions to optionally remove those from history (at least in a private channel)? Might also be a good 
place for the download of conference summaries.

I'm not really sure yet how that would work, as switching video on and off shouldn't cause too much 
noise and activity in the chat. Maybe when a conference lasts longer than a certain amount of time, 
with at least 2 participants, that it should leave some conference stats or that the conference stats 
are not part of the chat at all, but separate info in the context panel. 

> 
> The obvious conclusion is that Zulip causes alcoholism.
It is at least a good excuse for a drink at the pub :)


  reply	other threads:[~2025-11-03 19:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <176203615432.1342.6109094997293548870@gauss>
2025-11-02  9:44 ` Juliusz Chroboczek
2025-11-02 17:33   ` Jeroen
2025-11-03 11:39     ` Juliusz Chroboczek
2025-11-03 19:54       ` Jeroen [this message]
2022-01-21 19:26 [Galene] " Jeroen van Veen
2022-01-22 19:29 ` [Galene] " Juliusz Chroboczek
2022-01-24 16:00   ` Jeroen van Veen
2022-01-24 18:49     ` Juliusz Chroboczek
2022-01-24 19:00       ` Juliusz Chroboczek
2022-01-25  8:23       ` Jeroen van Veen

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='J4mx_gjsRvJNKtiyYXXlm06UyTKzTm-XwYvxbnrGuLiOXVUlnjiHxxZHgYw44DZSHpL2LUcqUroDB-Vo4bjXaAqBPBLMOxwLVLUPkZGq-ks=@garage44.org' \
    --to=jeroen@garage44.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