From: aeadio <aeadio@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Chromium - google will limit access to private API (no sync...)
Date: Fri, 29 Jan 2021 20:20:33 +0100 [thread overview]
Message-ID: <20210129192033.noz54kPuspn5mL5DGgAzoJLPGOsmgBRZ-r3WDL233MM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28233@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]
New comment by aeadio on void-packages repository
https://github.com/void-linux/void-packages/issues/28233#issuecomment-769999064
Comment:
> Perhaps even drop the chromium package.
The Chromium core browser is still fully functional. This just forbids access to premium Google features like built-in full-page translate, and profile sync across devices / platforms.
I think it's absurdly reactionary to consider removing the browser or pushing forks on Void's users that (1) may have less competent maintainers behind them, (2) may lag behind in security updates and (3) are going to lack those same features anyway.
Some other distros have taken the opportunity to make a political statement against Google's actions here, and that's admirable and all -- Google absolutely is pulling the rug out from legitimate users here -- but the scope of impact is a lot smaller than is being suggested in some heated Internet conversations, and a distro's package repository is no place to take a political stance at the expense of users.
next prev parent reply other threads:[~2021-01-29 19:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 8:54 [ISSUE] " jirib
2021-01-26 15:22 ` pbui
2021-01-26 15:31 ` ericonr
2021-01-26 16:24 ` pullmoll
2021-01-26 16:24 ` pullmoll
2021-01-26 16:48 ` tarkov2213
2021-01-26 17:12 ` tarkov2213
2021-01-26 20:10 ` tarkov2213
2021-01-29 19:20 ` aeadio [this message]
2021-01-29 19:22 ` aeadio
2021-01-29 19:48 ` pbui
2021-01-30 10:11 ` jirib
2021-02-01 9:42 ` Gottox
2021-02-02 1:41 ` tarkov2213
2021-02-07 23:20 ` ericonr
2021-02-08 14:07 ` jirib
2021-02-09 2:02 ` ericonr
2021-02-09 2:02 ` [ISSUE] [CLOSED] " ericonr
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=20210129192033.noz54kPuspn5mL5DGgAzoJLPGOsmgBRZ-r3WDL233MM@z \
--to=aeadio@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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).