From: Juliusz Chroboczek <jch@irif.fr> To: Jeroen van Veen <jvanveen@protonmail.com> Cc: "galene@lists.galene.org" <galene@lists.galene.org> Subject: [Galene] Re: Pyrite - experimental frontend for Galene Date: Fri, 05 Feb 2021 19:43:41 +0100 [thread overview] Message-ID: <87im76qrs2.wl-jch@irif.fr> (raw) In-Reply-To: <Dkqq-wYz6N1B1THWpk3nK5utmSeM1xJ26yobZMRJwPViKnIK5irhjyauiLedzvQVHbtDwUbqIkpKKu8qUgQzsoKrxnMKwLWuwT2HAyoCIUk=@protonmail.com> > * 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. > * 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. > 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. > * Recording UI Please clarify. -- Juliusz
next prev parent reply other threads:[~2021-02-05 18:43 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 [this message] 2021-02-06 19:52 ` Jeroen van Veen 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: 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=87im76qrs2.wl-jch@irif.fr \ --to=jch@irif.fr \ --cc=galene@lists.galene.org \ --cc=jvanveen@protonmail.com \ --subject='[Galene] Re: Pyrite - experimental frontend for Galene' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox