[arch-general] [arch-dev-public] Chromium losing Sync support on March 15

Morten Linderud foxboron at archlinux.org
Tue Jan 26 21:46:52 UTC 2021

On Tue, Jan 26, 2021 at 10:31:37PM +0100, Geo Kozey via arch-general wrote:
> > From: Levente Polyak via arch-dev-public <arch-dev-public at lists.archlinux.org>
> > On 1/26/21 9:53 PM, Morten Linderud via arch-dev-public wrote:
> > > 
> > > It's dissapointing frankly.
> > > 
> > 
> > Disappointing doesn't really catch it tho. If it would be just about the
> > sync functionality: so be it. But crippling the API usage on a level
> > that rips out especially things like the safe browsing functionality as
> > well places chromium knowingly and forcefully into a position that
> > doesn't make it viable to be distributed to users.
> Didn't google already make it clear it's only about sync api and the rest
> including safe browsing is perfectly fine to use with current keys if you
> don't remove them[1]?
> I think some people here overdramatize this situation. Users who depend
> on sync would have to switch to chrome but for majority nothing will change
> unless you indeed drop the package which hardly helps to limit damage.

Evangelos isn't subscribed so I'm paraphrasing from what he wrote on IRC.

The non-oauth api key will continue to work for now. This includes safe browsing. 


    1) We don't know for how long

    2) Supposedly it's for non-commercial use

    3) Jochen says it's ok to keep it, but he also said that 2013's chrome team
       didn't have the authority to alter the ToS.

    4) Support will likely be non-existent (similarly to how we had no
       geolocation for the first half of 2020)

Morten Linderud
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.archlinux.org/pipermail/arch-general/attachments/20210126/da40a1fa/attachment.sig>

More information about the arch-general mailing list