From: ludo@gnu.org (Ludovic Courtès)
To: ng0 <ng0@infotropique.org>
Cc: 28479@debbugs.gnu.org
Subject: bug#28479: icecat-52.3.0-gnu1 includes Google in search engines
Date: Mon, 18 Sep 2017 10:08:12 +0200 [thread overview]
Message-ID: <87tw00pgyb.fsf@gnu.org> (raw)
In-Reply-To: <20170918071100.hm4z3qjmmrkwvxh2@abyayala> (ng0@infotropique.org's message of "Mon, 18 Sep 2017 07:11:00 +0000")
Hello,
ng0 <ng0@infotropique.org> skribis:
> Mark H Weaver transcribed 0.4K bytes:
>> Hi,
>>
>> ng0 <ng0@infotropique.org> writes:
>>
>> > Is this an upstream bug? Should we patch to remove Google?
>> >
>> > I've just compared a completely new system (and Icecat profile)
>> > with my default profile, both include Google in search engines.
>> >
>> > There's also Bing and Yahoo, I'm not sure if all 3 were present
>> > before this version.
>>
>> Why would it be considered a bug to give users the convenient option to
>> use those search engines?
>>
>> Mark
>
> For example the branch of firefox which Parabola distributes
> makes changes not to default to Google. People rarely
> change defaults, so we should give the option to use Google
> but default to for example searx.me or duckduckgo.com.
I sort-of agree with both of you. :-)
Using a centralized search engine, be it Google or DuckDuckGo or even
searx.me, is a threat to privacy. Of course the dominating position of
Google makes it worse than the others, but let’s not pretend the others
are white as snow.
Besides, this is a discussion to have with IceCat upstream IMO. There’s
nothing Guix-specific here. So I’d close this one as “wontfix”.
WDYT?
Ludo’.
next prev parent reply other threads:[~2017-09-18 8:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-17 12:40 bug#28479: icecat-52.3.0-gnu1 includes Google in search engines ng0
2017-09-18 4:22 ` Mark H Weaver
2017-09-18 7:11 ` ng0
2017-09-18 8:08 ` Ludovic Courtès [this message]
2017-09-18 9:06 ` ng0
2017-09-18 17:12 ` Mark H Weaver
2017-09-18 17:25 ` ng0
2017-09-18 21:18 ` Mark H Weaver
2017-09-29 3:52 ` Mark H Weaver
2017-09-29 9:57 ` ng0
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=87tw00pgyb.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=28479@debbugs.gnu.org \
--cc=ng0@infotropique.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.