Hacker News Reader

Comment by bilekas | Hacker News Reader

They also have added replies which have been removed, reading the article it's actually not as conspiratorial as you make it seem.

In this case I really think it prudent to assume the worst from Google as they don't really have a positive history for walling off users data, be it personal email or phone meta information.

> "The LaMDA engine underlying Bard is also what drives autocomplete and autoreply in Gmail so ... yeah Bard's training data includes Gmail. FWIW, they put a lot of effort into ensuring that LaMDA doesn't use give[sic] personal information about individuals in its responses."

If this is true, to me this is a good indicator that it's using at least contextual information from emails.

View on HN

> I really think it prudent to assume the worst...

This is not evidence-based thinking and leads to heavy biases.

Who wrote that reply? A Googler? Is there a screenshot? This would be a gigantic GDPR lawsuit.

This reminds me of not communicating with Gmail users. Gmail has been evil forever since "personalized" ads.

It's in the article, but here's the direct link to help you out.

https://twitter.com/cajundiscordian/status/16382433030356705...

At the moment, for some reason Google seems almost untouchable.

I mean, single handedly destroying the browser market by deceit and abuse of market position in broad daylight, you'd think sooner or later EU or someone would force them to pay and put up a browser ballot on Google.com, but so far, no.

Luckily the French consumer protection agency has at least forced them to implement the cookie question thing almost so we can now reject all right away.

> single handedly destroying the browser market by deceit and abuse of market position in broad daylight

It's not single handedly, it's every developer handedly.

First thing any dev does is install Chrome, and make their normal friends install Chrome, even when -- for example -- it destroys the battery life on their Macbook while breaking a variety of usability conveniences. When pressed, it turns out most of this is cargo culting, they actually haven't turned on developer tools or compared performance or memory handling, much less experienced the remarkable security and privacy integrations* available in co-shipped Safari browser.

Having observed the browser wars since before NCSA Mosaic, I'd argue not Google but a set of "tech influencers" well represented on HN made this happen, not Google.

In the longer context, HN's clamor to force iOS off Safari, the only significant bastion against a monoculture and one ad company's complete grip on visibility of all web use, is shocking.

---

* For instance, various anti-tracker and IP anonymizing capabilities, plus a built-in and cross device syncing password manager that even supports TOTP codes.

> First thing any dev

Maybe frontend devs. For me FF is invaluable, especially the containers.

Citation required. I've been warning my circles off Chrome for years. Firefox is generally my go to.

> This would be a gigantic GDPR lawsuit.

No. They are not available in the EU.

At least, I assume this is how Google thinks about it.

It doesn't matter, and Google knows it.

I believe the point is that Google leaks data collected through a service available in the EU (Gmail). The GDPR claim would be related to gmail, not bard.

If anything, bard not being available in the EU would prove that using the data wasn't necessary for EU's gmail service.

Reply on news.ycombinator.com