From: Marco van Hulten <marco@hulten.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: ungoogled-chromium
Date: Sun, 22 Mar 2020 13:58:14 +0100 [thread overview]
Message-ID: <20200322135814.365cea29@hulten.org> (raw)
In-Reply-To: <87k13clg4b.fsf@elephly.net>
Ricardo—
Je 22 Mar 13:37 skribis Ricardo:
> > I installed ungoogled-chromium. When it starts and I browse to the
> > main Jitsi instance [1], it wants to install the extension for Google
> > Calendar and Office 365 integration. I don't know if those are
> > non-free softwares, but they at least provide non-free web services.
>
> It seems to me that these suggestions are triggered by the website.
> We don’t attempt to filter website contents.
Thanks for this info, also Marius. Then there is no issue with the
ungoogled-chromium package.
I might look into what meet.jit.si is doing.
—Marco
next prev parent reply other threads:[~2020-03-22 12:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-22 12:02 ungoogled-chromium Marco van Hulten
2020-03-22 12:17 ` ungoogled-chromium suggests extension Marco van Hulten
2020-03-22 12:31 ` ungoogled-chromium Marius Bakke
2020-03-22 12:37 ` ungoogled-chromium Ricardo Wurmus
2020-03-22 12:58 ` Marco van Hulten [this message]
2020-03-22 13:14 ` ungoogled-chromium Vagrant Cascadian
2020-03-22 14:16 ` ungoogled-chromium Marius Bakke
2020-03-22 16:18 ` ungoogled-chromium Marco van Hulten
-- strict thread matches above, loose matches on Subject: below --
2019-04-19 22:19 ungoogled-chromium Mason Hock
2019-04-20 0:54 ` ungoogled-chromium beoram
2019-04-20 7:27 ` ungoogled-chromium Ricardo Wurmus
2019-04-20 18:12 ` ungoogled-chromium Mason Hock
2019-04-20 19:59 ` ungoogled-chromium Julien Lepiller
2019-04-20 20:10 ` ungoogled-chromium Mason Hock
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200322135814.365cea29@hulten.org \
--to=marco@hulten.org \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).