[pgeorgi]

> Except they have an offering in the market for other people to do just that.

bard.google.com states right on the front page: "Bard is an experiment and may give inaccurate or inappropriate responses."

Also, the warning is about _all_ LLMs.

[ineedasername]

And google is nonetheless happy to have countless other coders use their experiment, just not their own.

Leave other LLMs to the side on this issue. There are a variety of different issue that arise when Google employees might use a non-Google LLM, so that prohibition is in a category with different reasons.

[pgeorgi]

> And google is nonetheless happy to have countless other coders use their experiment, just not their own.

What makes you think so? Those LLMs aren't primarily coding tools.

> Leave other LLMs to the side on this issue

https://www.reuters.com/technology/google-one-ais-biggest-ba... indicates that the ban is about "all LLMs, period".

It's ElReg who, true to their style, decided to focus the discussion on Google employees using (or not using) Google's LLM. Even they, however, acknowledge that Google "also advised users not to include sensitive information in their conversations with Bard in an updated privacy notice."

As such, Google seems to apply the same standard to other users (including "countless /other/ coders") that it applies to its employees, no?

[ineedasername]

>aren't primarily coding tools.

It doesn't have to be a primary use case for it to be one of the use cases Google is putting forward. In which case Google is still saying they're unwilling to use their own tools in the way put forward for others to do so.