Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Jeroen van Veen <>
To: Juliusz Chroboczek <>
Cc: "" <>
Subject: [Galene] Re: Pyrite - experimental frontend for Galene
Date: Sat, 06 Feb 2021 19:52:57 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
Op vrijdag, februari 5, 2021 7:43 PM, Juliusz Chroboczek <> schreef:

> > * Show roles next to users (is this information available? I only can
> > -   see my own user's present/op permission)
> It's not available. I agree that it should be, except if somebody thinks'
> it's a privacy violation.

Would be great! Having the permission info per user available would make
implementing user context actions much easier/useful I suppose.

> > -   Think of some UI-elements for some commands (e.g. user context actions)
> Yes. That's something that's badly needed.

> > -   Add file sharing (is this possible yet with Data Channels?)
> Depends if you want the file to flow through the server, or to go directly
> peer-to-peer. I'm planning to implement it as peer-to-peer, in which case
> no changes to the server are needed — use the "userMessage" message to do
> your signalling.
> Please make sure you document your signalling protocol, so we can use the
> same one.

Good idea to do this p2p indeed. Would love to try this out and document it.
May take me some time to get at that point though.

> > For these features, a REST'ish API with json returns would be nice:
> >
> > -   Administrator UI for groups
> I don't want this implemented in the server: have a second process that
> does the administration. Galène will pick up the changes made to the
> on-disk JSON files after a few seconds.

Alright. Sounds like a nice mini project to write in Go :)

> > -   Recording UI
> Please clarify.

I figured it would be a nice feature to have the stats and recordings list
as a single-page view inside Pyrite, just for the people who have the role access
rights. Iirc, the recordings page is flat html, which is fine, but to consume it
in an existing app, it may be easier to have a json representation of the recording
files. Another direction may be to implement this in a second process, because the
information is all on disk already(just like with the admin ui). I suppose that
would be the way to go.

> -- Juliusz
> Galene mailing list --
> To unsubscribe send an email to

  reply	other threads:[~2021-02-06 19:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-16 17:33 [Galene] " Jeroen van Veen
2021-01-16 18:10 ` [Galene] " Juliusz Chroboczek
2021-02-05 16:35   ` Jeroen van Veen
2021-02-05 18:43     ` Juliusz Chroboczek
2021-02-06 19:52       ` Jeroen van Veen [this message]
2021-02-06 20:21         ` 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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \
    --subject='[Galene] Re: Pyrite - experimental frontend for Galene' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox