From: Juliusz Chroboczek <jch@irif.fr>
To: Stefan Bethke <stb@lassitu.de>
Cc: galene@lists.galene.org
Subject: [Galene] Re: Examples for one to many distribution?
Date: Sat, 16 Nov 2024 15:39:01 +0100 [thread overview]
Message-ID: <875xonqm4a.wl-jch@irif.fr> (raw)
In-Reply-To: <694C8C7A-D0C2-4E20-BF31-6698EAC7372C@lassitu.de>
Hello Stefan,
> I'm trying to create a setup where I feed audio into an SFU, and people
> can connect to the SFU and listen to the audio.
Where does the audio come from?
> * have a minimal user interface, where users simply choose the group they would like to listen to
> * only have audio playing, no video
> * disable all other features like chat
I think the current client can do that
1. set the "public" flag on your groups to true, this will cause the
groups to appear on the landing page;
2. only send audio to the group, this way no video will be played;
3. give your users the "observe" permission, so they cannot open new
streams or add messages to the chat:
"users": {
"bob": {
"password": ...,
"permissions": "observe",
}
}
> Are there examples that I could base a custom frontend on, apart from
> the minimal client?
The minimal client should be a good starting point, at least that's what
I wrote it for. Please let me know if there's anything that's not clear.
> I'm happy to customize Go and JS/TS code, or even write something from
> scratch, but I would be really happy to customize something existing.
I suggest you start with the full client configured as above, and then
we can think together about what further changes are required.
Regards,
-- Juliusz
next prev parent reply other threads:[~2024-11-16 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-16 12:09 [Galene] " Stefan Bethke
2024-11-16 14:39 ` Juliusz Chroboczek [this message]
2024-11-16 14:45 ` [Galene] " Stefan Bethke
2024-11-16 16:07 ` Juliusz Chroboczek
2024-11-16 16:46 ` Tim Panton
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=875xonqm4a.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=galene@lists.galene.org \
--cc=stb@lassitu.de \
/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