When content comes to you, lots of things change.

· Bits and Bobs 4/8/24

Imagine your friend has a blog that has lots of rich insights.

Someone could create a Chrome Extension based on that content.

Whenever you're reading a page, it would see if there's a relevant insight from that content and display it.

The right insight at the right moment could plausibly be magical.

This model has some problems.

First, installing the extension is very high friction. I have to:

Hear about the extension

Decide it might be useful in some abstract, fuzzy way in the future

Install the extension

This requires a strong primary use case to get over that hump, some acute user need–which most users, even close friends of the author, wouldn't have in this case.

Also, the extension, once installed, will likely over-trigger.

The extension's entire reason to exist is to share insights relevant from its author's content.

In the same way that everyone thinks they're special, the extension's logic is "my entire reason for being is to show these insights, I should do it whenever I think it's useful."

But this will likely lead to significant over-triggering.

The extension's triggering logic is content-centric.

After a few too many distracting triggers, even the most motivated user will uninstall the extension in frustration.

But imagine instead someone creating a recipe that your personal AI can take note of.

Your own personal AI can run the recipe in the background, and then decide if it makes sense to show it to you at that moment.

The extension trigger logic is user-centric.

Your personal AI could develop a better and better model of what kinds of content, from which authors you find relevant, and trigger only in the cases it is very likely to be useful.

Your personal AI could do a significantly better job managing your personal attention preferences than any swarm of content-centric extensions could ever do.

To know when to trigger, you need a holistic sense of what the user wants and what else is available.

A single extension only knows its own context, not the overall context of the user and what else could be shown.