I did a different thing. when parallel work gets to much I add a manager agent Infront. it manages all requests and coordinates with me.

pinhole is great but if the device fails your network is down. I swapped to nextdns because of that. maybe support of multiple devices would fix it - now that is this cheap it would not matter .

The simple answer is have 2. If the cost per unit is low enough than deploying 2 PiHoles is trivial.

The developers could make users' lives easier by implementing a clustering option that syncs the 2 out of the box. For static deployments, where you don't change the config too often, it's still decent as it is.

I did the same (until my RPi zero stopped working). Both the devices share same vertical IP address and if one ever went down, the other would take over without any delay.

I have my router set up to send DNS requests to my adguard home server, and if there's no response, it falls back to one of Cloudflare's. So it fails-open, letting the ads in along with normal requests.

You can have a 2 adguard home + adguard-sync. Works smoothly.

But what if both fail? :)

I also currently run multiple Claude sessions with Fabel as the brain coordinating the manager sessions which in turn spawn sub agents.

Check out jwillmer/ai-status at GitHub @bottlepalm. It helps keep track of all the small fixes that are going on simultaneously. I crated the tool for me since I have similar workflows.

This is great. I build a Ai status page [1] based around MD files and included obsidian as option. Will look to support this as well.

[1]: https://github.com/jwillmer/ai-status

We recently started home renovation and needed a todo app to keep up with the tasks. I noticed that the existing todo apps are annoying to use and lacking a good ai integration. So I started vibe coding my own app. Fully offline capable and with ai integration at its core.

I run it at https://ferdig.de

After the license change we switched to Elsa and contribute code together with other companies that made the switch. https://elsaworkflows.io

I did something similar in the past and called it emergency contacts [1]. Basically a encrypted json that can be decrypted online. I use it to store emergency contact information in case I got stranded without any own device at hand.

[1]: https://github.com/jwillmer/emergency-contacts

Interesting! Never thought of adding important contact info to my emergency stash, but in retrospect it is a great idea.

Linked your project.

I did something like this in reverse a while ago. Every day the page will paint one pixel till the image reveals itself: https://jwillmer.de/blog/programming/every-day-a-pixel

On Android we use Throttly to mess with the network: https://play.google.com/store/apps/details?id=me.twocities.t...