From: Jeroen van Veen <firstname.lastname@example.org> To: Juliusz Chroboczek <email@example.com> Cc: "firstname.lastname@example.org" <email@example.com> Subject: [Galene] Re: Pyrite - experimental frontend for Galene Date: Fri, 05 Feb 2021 16:35:42 +0000 [thread overview] Message-ID: <Dkqq-wYz6N1B1THWpk3nK5utmSeM1xJ26yobZMRJwPViKnIK5irhjyauiLedzvQVHbtDwUbqIkpKKu8qUgQzsoKrxnMKwLWuwT2HAyoCIUkfirstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> I replaced the npm/unpkg workflow with a simple deployment service to learn more about Go (https://github.com/garage44/rand). The files are now hosted locally by nginx instead of being proxied through unpkg, which should make it much more responsive/reliable. Updates are much easier/faster to deploy now. In the meanwhile i18n(dutch), a PWA installer, Chat/commands and some tweaks were added to Pyrite. A lot of stuff that doesn't work (properly) yet, but so far it's been a fun side-project to work on! Some thoughts about what I would like to build next: * Show roles next to users (is this information available? I only can see my own user's present/op permission) * Think of some UI-elements for some commands (e.g. user context actions) * Keep up with the latest Galene frontend changes * Add file sharing (is this possible yet with Data Channels?) For these features, a REST'ish API with json returns would be nice: * Administrator UI for groups * Recording UI ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ Op zaterdag, januari 16, 2021 7:10 PM, Juliusz Chroboczek <firstname.lastname@example.org> schreef: > > https://pyrite.video/ > > The server said: not authorised.
next prev parent reply other threads:[~2021-02-05 16:35 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 [this message] 2021-02-05 18:43 ` Juliusz Chroboczek 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='Dkqq-wYz6N1B1THWpk3nK5utmSeM1xJ26yobZMRJwPViKnIK5irhjyauiLedzvQVHbtDwUbqIkpKKu8qUgQzsoKrxnMKwLWuwT2HAyoCIUkemail@example.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --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