That looks very cool and maybe worth porting what I currently do — I just run a super simple template and each recipe is its own include file, with an auto generating index.

Even if the hosting dies the recipes are easy to read on github, and the network availability makes shopping easy if I decide I want to get ingredients for it at a store, or to share.

I’m not worried about some nebulous theft; the not sharing of a card number with a merchant is what I’m referring to.

Thanks! That’s an important consideration that I hadn’t run across.

I don’t use a phone case and it’s less secure besides.

I use Kagi too, it’s great.

The other commenter corrected your index note.

What I found most illuminating was a comment by the CEO in an interview, perhaps The Verge? The TLDR of it was that Google makes money when you dwell on their site (so they want the highest ad serves per search), and a paid search engine loses money every page they have to serve you (so they want to give you your answer fast).

So, the user and Google are at odds, and the user and Kagi have the same goal.

It’s tap to pay (or use the public transit) that’s keeping me back.

Why Molly over the official client, may I ask? The official client is already OSS.

I only read about that today, so I hadn’t even considered that angle. They’re doing some cool stuff in that space. jeff is the self-hostable one that does best as far as I know.

Both are reasonable, though I understand why Google is pushing back against it.

The assistant angle simply is saying that they have to expose APIs that they are already using and that they can’t lock away those features, especially on an open-source operating system.

On the second point, it’s just mitigating the first-mover advantage — just because Google existed before something else, potentially before an inventor-of-a-competitor was even born, doesn’t mean that they should be immune to competitive pressure.