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: Sat, 06 Feb 2021 21:21:54 +0100 [thread overview] Message-ID: <87sg69hrq5.wl-jch@irif.fr> (raw) In-Reply-To: <x7KEY4G590Fn08JwYbFl736msIF7n_U2lgcHZci-y1AkC_I5twQYJhBXpgJNYgsKcqpYzakMkIIl2VS1CLBc0ozFJSNyrR29bw1vnkcwcXM=@protonmail.com> >> 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. Uh-huh. Also, the ability to send chat messages should be an explicit permission. Anyone see any objections for privacy reasons? >> > 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 :) The alternative would be for the server to allow GET/PUT of the JSON files, so that you can write your administration interface entirely in the client. With a little help from If-Match, this could be made safe against lost updates. Whatever we choose to do, the ability to modify the on-disk JSON files and have Galène pick up the changes with no user intervention will remain. I like it. >>> - Recording UI > I figured it would be a nice feature to have the stats and recordings > list as a single-page view inside Pyrite, [...] > 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 haven't though about it seriously, but a JSON index of the files is a good idea. -- Juliusz
prev parent reply other threads:[~2021-02-06 20:21 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 2021-02-06 20:21 ` Juliusz Chroboczek [this message]
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=87sg69hrq5.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