—
no predictions resolved yet
0 pending · 0 expired
Yep. Well, maybe not everyone, but many people are going to have barbecues. As you dream about that long weekend that you're about to engage in, like having a little bit of extra visual stimulus makes it a little bit more fun and more enjoyable. And so that's why you get something like images and responses. And so we're going to continue to build compound and just keep listening to how people are responding, what they want to do, what they want to grow and iterate. And of course we want to be he
one of the things that we are excited about is this notion of bringing tool use into BART. How can you get it to a point where as you have interactions like this and kayak, uh, one of the partners that, um, you know, we're talking about, uh, bringing, bringing to the full, how do you make sure that the experiences that you're getting are trustworthy, are reliable, are getting there. And that's where you need to focus now, where we need to focus now, making sure that the responses that you're get
The monetization plan for anything we do at Google follows the same rubric, look to where you're generating value for people and make sure that the way that you monetize falls in line with that. And so that's how, uh, that's how we're going to approach it. We're focused on driving the value and respecting the opportunity means that when we're, we're ready to fold that in, it'll be folded in.
And one of the features that we built in along with that, uh, was this notion to export directly into Colab. So Colab is a mixed notebook and, uh, Python ID, uh, for that. Google has created where you see a Python script and there's an export button at the bottom. You can export, go directly into Colab and start iterating.
And so we're watching it speed up people's process. And it's really inspiring.
So code has been live for a few weeks now. When we launched the Bart experiment, we didn't feel like the experiment, the experience was helpful enough. Uh, I think it was three or four weeks after the experiment launched, we gave the, we gave Bart the ability to code or release the ability for Bart to code. And it quickly became one of the most popular ways to engage with Bart.
one of the tabs that you see on barred is barred activity, and you can see what are the, what are the conversations that you've had and you give users the choice of, Hey, if I, if I want to be a part of this experiment, but I feel very strongly that I don't want this information to be locked. Then you give users that choice. It's critical. That's part of respecting the user and why it's been there since the day that the experiment launched.
And so while we build the technology, we also have to build that respect for the user to make sure that, Hey, if you're going to trust us with using this tool, we're going to be extremely clear how your most private and personal information is being used. And so, um, we don't want to, we don't want to put it in people's hands before we feel like that, that design element is, is, uh, confidently in people's hands.
the thing that enables this is Bard's ability to translate between natural language and code and start to quote unquote think. They're not sentient, but they, uh, start to produce logic results in, in the form of code. As it does that, you can start to ask it to write code to interact through the APIs that exist, et cetera.
If you're going to start having a language model, access your email and interact with that email and produce a result, the user needs to be in control. Now that's the first principle for which we're building. The user is in control and you have to be transparent. What information is being seen and how's it, how's it being used? Those are the two guiding principles of bringing an extremely powerful technology like this to people. And it's not just Gmail. There are plenty of tools across Google, u
we announced the ability, uh, for barred to access tools at Google IO a couple of weeks ago. So the good news is it's coming. It's coming.
We only succeed when others succeed. That's been at the DNA of this company for the 25 years that it's been around.
we're not launching this without testing it with our team inside of Google, going through the red teaming exercises that are critical in the development.
You can look at the speed of delivery. We're obviously very proud of being able to get technology in people's hands. But it's really about the speed of insight that we're focused on.
Images started two days ago, three days, Tuesday of this week.
We have six products with over 2 billion users, 15 products with over half a billion users.
we felt it was critical to launch it without making a promise of, hey, this is a product because we don't believe that the technology as it stands today and a direct access to a large language model should be a product. It needs a lot of work and iteration. And the Bard experiment is here to get the feedback, start the conversations and continue to build and iterate and apply those lessons to not only making Bard better, but across all of Google's products.