High Signal Podcasts Evidence ledger
Method
Browse
← Back to evidence

Evidence receipt / preference

Published · transcript-backed

Aravind Srinivas: preference

19 Jun 2024 Lex Fridman Podcast #434 – Aravind Srinivas: Perplexity CEO on Future of AI, Search & the Internet

“The Google presents this information in cool widgets, and I think that is where this is a very different problem from just building another chat bot.”

— Aravind Srinivas

Source trail

Everything needed to verify it.

Speaker
Aravind Srinivas
Attribution
Verified speaker
Claim type
preference
Recorded
19 Jun 2024
Publisher
Lex Fridman Podcast

Transcript context

…Realtime information, Google excels in providing realtime information like sports score. While I think Perplexity is trying to integrate realtime, like recent information, put priority on recent information, that’s a lot of work to integrate. Exactly, because that’s not just about throwing an LLM. When you’re asking, “Oh, what dress should I wear out today in Austin?” You do want to get the weather across the time of the day, even though you didn’t ask for it. The Google presents this information in cool widgets, and I think that is where this is a very different problem from just building another chat bot. The information needs to be presented well, and the user intent. For example, if you ask for a stock price, you might even be interested in looking at the historic stock price, even though you never ask for it. You might be interested in today’s price. These are the kind of things that you have to build as custom UIs for every query. Why I think this is a hard problem, it’s not just the next generation model will solve the previous generation models problem’s here. The next generation model will be smarter. You can do these amazing things like planning, query, breaking it down to pieces, collecting information, aggregating from sources, using different tools. Those kinds of things you can do. You can keep answering harder and harder queries, but there’s still a lot of work to do on the product layer in terms of how the information is best presented to the user, and how you think backwards from what the user really wanted and might want as a next step, and give it to them before they even ask for it. I don’t know how much of that is a UI problem of designing custom UIs for a specific set of questions. I think at the end of the day, Wikipedia looking UI is good enough if the raw content that’s provided, the text content, is powerful. If I want to know the weather in Austin, if it gives me five little pieces of information around that, maybe the weather today and maybe other links to say, “Do you want hourly?” Maybe it gives a little extra information about rain and temperature, all that kind of stuff.…

Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.

Search evidence