From: Juliusz Chroboczek <jch@irif.fr> To: "email@matrix8.org" <email@matrix8.org> Cc: galene@lists.galene.org Subject: [Galene] Re: Talk about Galène today (monday) at 17pm CET Date: Tue, 02 Mar 2021 07:14:10 +0100 [thread overview] Message-ID: <878s7613rh.wl-jch@irif.fr> (raw) In-Reply-To: <81FD70ED26B7687E7927C74@matrix8.org> Hi, Thanks for your comments, they are useful. > The first thing I researched on was to see if my usual preferred Debian > is OK to run Galene. I found out that no particular Linux distro was > recommended on official Galene site. Point taken -- I'll make it clear in the doc that Galène works on any Linux distribution, on BSD Unix, on Mac OS X, and on Windows. > Then I started to research on preferred version of Go. Right. I need to make it clear that Go 1.13 or later is required on the host that is used for compilation, and that nothing (except the kernel and Galène itself) is required on the host that runs Galène. > It was my first time to touch Go so I wanted to do some research on the > background of Go language especially to see if there is any privacy > breaching string attached to Google, the mother of Go. The dependencies are downloaded from Google's servers. You can disable this functionality, but then the dependencies will be downloaded from Microsoft Github. We're stuck between a rock and a hard place. > Today I have been enjoying learning how to write JSON dictionary correctly Okay, that's a different issue: we need a user-friendly way of defining groups for Galène. This is one of the most important remaining missing bits. > I also want to share that I had to replace the original self-signed > certificate Right. Galène works fine with a self-signed certificate, but the browser vendors display a huge red warning (even though self-signed certificates are way more secure than plain (unencrypted) HTTP). I'll make it clear that while self-signed certificates are fine for testing, for production usage you need a real certificate. Thanks again for your comments, -- Juliusz
next prev parent reply other threads:[~2021-03-02 6:14 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-22 13:32 [Galene] " Juliusz Chroboczek 2021-02-22 13:49 ` [Galene] " Gabriel Kerneis 2021-02-22 14:04 ` Juliusz Chroboczek 2021-02-22 17:07 ` Juliusz Chroboczek 2021-02-22 17:24 ` Michael Ströder 2021-02-22 17:32 ` Juliusz Chroboczek 2021-02-22 18:00 ` Michael Ströder 2021-02-22 18:15 ` Juliusz Chroboczek 2021-03-01 19:38 ` email 2021-03-02 6:14 ` Juliusz Chroboczek [this message] 2021-03-02 7:29 ` eric_G 2021-03-02 15:37 ` Juliusz Chroboczek 2021-03-02 16:55 ` Dave Taht 2021-03-02 17:21 ` Juliusz Chroboczek 2021-03-02 17:40 ` Dave Taht 2021-03-02 18:24 ` Nils Andreas Svee 2021-03-02 18:58 ` Sean DuBois 2021-03-02 19:06 ` eric_G
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=878s7613rh.wl-jch@irif.fr \ --to=jch@irif.fr \ --cc=email@matrix8.org \ --cc=galene@lists.galene.org \ --subject='[Galene] Re: Talk about Galène today (monday) at 17pm CET' \ /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