Live data from Hacker News

'Phased Out'–Google Confirms Bad News for All 3B Chrome Users

forbes.com

11–20 of 21 posts

Re: 'Phased Out'–Google Confirms Bad News for All 3B Chrome Users

#11

I hope this news travels to more gen pop. My 82yo MIL uses Firefox because she’s concerned about the acceleratingly encroaching “police state”. That being said as an IT manager, it’s hard to tell my employees to incur the friction of broken Google services (Meet, a few others) for the intangible privacy benefits.

What Google services are broken on Firefox? My anecdata is that GSuite works completely fine daily driving Firefox.

Maps is the most frequent offender of something that is "kinda broken" on Firefox - black tiles/boxes, slowness, other things not rendering right. But on Chrome, it works fine 100% of the time.

Re: 'Phased Out'–Google Confirms Bad News for All 3B Chrome Users

#12

I hope this news travels to more gen pop. My 82yo MIL uses Firefox because she’s concerned about the acceleratingly encroaching “police state”. That being said as an IT manager, it’s hard to tell my employees to incur the friction of broken Google services (Meet, a few others) for the intangible privacy benefits.

Google meet works perfectly fine for me on Firefox

Re: 'Phased Out'–Google Confirms Bad News for All 3B Chrome Users

#14
Forbes is blog-spam. Official blog-post: https://privacysandbox.com/news/update-on-plans-for-privacy-...

>We believe the proposed interoperable Attribution standard has the potential to support this objective in a privacy-preserving fashion, and we'll continue to engage on it through the web standards process in collaboration with a wide range of stakeholders including other browser makers.

>After evaluating ecosystem feedback about their expected value and in light of their low levels of adoption, we've decided to retire the following Privacy Sandbox technologies: Attribution Reporting API (Chrome and Android), IP Protection, On-Device Personalization, Private Aggregation (including Shared Storage), Protected Audience (Chrome and Android), Protected App Signals, Related Website Sets (including requestStorageAccessFor and Related Website Partition), SelectURL, SDK Runtime and Topics (Chrome and Android).

Re: 'Phased Out'–Google Confirms Bad News for All 3B Chrome Users

#16
post #11

Earlier quoted context omitted.

What Google services are broken on Firefox? My anecdata is that GSuite works completely fine daily driving Firefox.

Maps is the most frequent offender of something that is "kinda broken" on Firefox - black tiles/boxes, slowness, other things not rendering right. But on Chrome, it works fine 100% of the time.

I have used Firefox on mobile and desktop for a better part of 15 years and I cannot recall seeing black boxes or tiles on Google Maps.

Re: 'Phased Out'–Google Confirms Bad News for All 3B Chrome Users

#18
post #12

I hope this news travels to more gen pop. My 82yo MIL uses Firefox because she’s concerned about the acceleratingly encroaching “police state”. That being said as an IT manager, it’s hard to tell my employees to incur the friction of broken Google services (Meet, a few others) for the intangible privacy benefits.

Google meet works perfectly fine for me on Firefox

And even on Safari. But there are indeed chrome-only features AFAIK.

Re: 'Phased Out'–Google Confirms Bad News for All 3B Chrome Users

#19

Please just make this a submission the source: Update on Plans for Privacy Sandbox Technologies https://privacysandbox.com/news/update-on-plans-for-privacy-...

I tried but hackernews dedupes submissions for posts. The original poster barely got attention with this source: https://news.ycombinator.com/item?id=45644530

Re: 'Phased Out'–Google Confirms Bad News for All 3B Chrome Users

#20
post #11

Earlier quoted context omitted.

What Google services are broken on Firefox? My anecdata is that GSuite works completely fine daily driving Firefox.

Maps is the most frequent offender of something that is "kinda broken" on Firefox - black tiles/boxes, slowness, other things not rendering right. But on Chrome, it works fine 100% of the time.

None of that happens for me.
Post reply on HN