I’m right there with you. Your comment gives me some confidence on this front to stage the upgrade this weekend.

A script checks container status and accessibility, and pushes a ntfy alert if it goes down. Healthchecks.io reports if the whole Pi goes down.

Also what I use on a Raspberry Pi 5.

Discord notifications also sometimes come with random delays because of Google bullshit, and ntfy supports UnifiedPush.

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 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.

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.