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

[David Runge]

On 2021-01-26 22:18:21 (+0100), Levente Polyak via arch-dev-public wrote:
> 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.
> 
> I'm incredibly mad that his is literally a situation where the open
> source world is soaked up and in return a big clear "screw you guys, we
> don't care" sign is raised. Well played, exploiting a monopoly position
> like this and literally cheating on the open source community all around
> them.
> 
> PS: firefox is affected by safe browsing keys as well.

I agree, that this situation and Google's position on this is utterly
disappointing.

However, I am one of the people that actually needs chromium for work
daily and that needs to rely on it for several websites that are not
supported by firefox (which I use mainly).

I suggest we all take a deep breath and evaluate the situation. Is
safe-browsing and geolocation in chromium and firefox really affected by
this? If so, that would of course be bad (from the reactions so far,
users seem mostly fine without the Google sync functionality).
However, we need to test this carefully with e.g. packages in [testing]
instead of prematurely deleting everything.

If e.g. safe-browsing is indeed affected, now would be the time to
contact mozilla about this to a) change this for firefox by default and
b) evaluate whether it is possible to e.g. use their services in
chromium.

If safe-browsing is not affected, under what circumstances are we
allowed to use and distribute a browser with it? The Google Chrome team
can and needs to answer these questions.

These are all things we need to figure out. Let's please not panic.

Best,
David

-- 
https://sleepmap.de
-------------- 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-dev-public/attachments/20210127/a2aee5a6/attachment.sig>