Github messages for voidlinux
 help / color / mirror / Atom feed
From: pbui <pbui@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Chromium - google will limit access to private API (no sync...)
Date: Tue, 26 Jan 2021 16:22:04 +0100	[thread overview]
Message-ID: <20210126152204.uId6HLzxrHPg5evHldXNp9GD94NhcEMYGrk0St3HBhE@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: 691 bytes --]

New comment by pbui on void-packages repository

https://github.com/void-linux/void-packages/issues/28233#issuecomment-767615980

Comment:
How about the following?

```
On March 15, 2021, Google will be limiting access to their private Chrome APIs:

    https://blog.chromium.org/2021/01/limiting-private-api-availability-in.html

This means that after this date, chromium users will no longer be able to take
advantage of features such as Google account sync (including bookmarks), spell
checking, translation, and safe browsing.

If you wish to utilize a chromium-based browser with those features, you will
need to build and install the restricted google-chrome package.
```

  reply	other threads:[~2021-01-26 15:22 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 [this message]
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
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 ` [ISSUE] [CLOSED] " ericonr
2021-02-09  2:02 ` 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=20210126152204.uId6HLzxrHPg5evHldXNp9GD94NhcEMYGrk0St3HBhE@z \
    --to=pbui@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).