From: Adam Thompson <arthompson1990@gmail.com>
To: Cleverson Casarin Uliana <cleverson@clul.router5.com>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: Edbrowse and privacy maximalism
Date: Mon, 21 Nov 2022 09:38:29 +0000 [thread overview]
Message-ID: <Y3tHFVrfybwRz4TI@pinebook-pro> (raw)
In-Reply-To: <MTAwMDA0NS5jbHVs.1668817096@quikprotect>
On Fri, Nov 18, 2022 at 09:18:07PM -0300, Cleverson Casarin Uliana wrote:
> Hi, I was reading the review linked below, and was wondering how Edbrowse
> compares against the very severe author's criteria for a privacy respecting
> browser. I might write to him later to ask him to include edbrowse on his
> review...
We don't make any unsolicited requests and definitely have no
dependencies on Google, Mozilla etc. However the author would class Edbrowse
as a minimalist browser (see the section on such things) and so I suspect
that any such message would meet with a negative response.
Cheers,
Adam.
prev parent reply other threads:[~2022-11-21 9:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 0:18 Cleverson Casarin Uliana
2022-11-21 9:38 ` Adam Thompson [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y3tHFVrfybwRz4TI@pinebook-pro \
--to=arthompson1990@gmail.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=cleverson@clul.router5.com \
/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 NNTP newsgroup(s).