I use Kagi as my daily driver on mobile, and have it constantly as my second browser (next to FF Dev) on desktop for the same reason I use Kagi Search, support of the concept. It doesn't hurt that the browser is pretty good performance and experience-wise.
More fascinating for me is this discussion thread, where there's legitimate debate around the need/expectation for alphabetical sorting to match/include lexical sorting.
I'm personally in the "want lexical as part of alphabetical" - as 'photo19' should come after 'photo2' in my expectations, but the number of cases cited where this doesn't/shouldn't work is enough to justify a degree of contextual or situation awareness that most systems and interfaces simply aren't designed to cater for (file-systems vs photo-storage applications).
Don't laugh, but in my org we have a bi-annual "Hive Week" where all Product/Tech (two sub-orgs) bring all the 'bees' home to Office Central for a week of, um, collaboration?
Funny how some things you were thinking about before you log-on for the morning suddenly become front-and-centre for you.
I have an old original iPad wall mounted showing an AppDaemon dashboard from my HomeAssistant. I wish the old Safari could handle a standard dashboard but alas. I even had to add a specific certificate to enable Safari to access and show things such as HTTPS feeds from my cameras.
Looking at the comments, there doesn't appear to be anyone who has solved this issue :(
I've walked the same rocky path and have the bleeding feet to show for it! My problem is that now my packaging/environment mental model is so muddled I frequently mix up the commands...
Adding my kudos to the other commenters here - the polymath skills necessary to take on something like this is remarkable as a solo effort. I was hoping for more detail on the issues found during the request/parsing at a domain/page level.
Almost ready to launch an all-in-one platform for solving problems I face all the time at work, with clients and my own sites.
Frustrated with running 10+ different checks on domains/websites I've built or working on with 10+ different services, I've built - with help from Claude Code - a Django app that tries to wrap all those key checks into one place. On top of that, I've built in scheduled monitoring and alerting.
It's been a great experience learning about the intricacies and nuances in different website set-ups, the complexities in avoiding false negatives, fun with CloudFlare workers, agentic coding and much more.
The site is still running off a RPi (Coolify) in my home-server behind a CF Tunnel at the moment, so won't link directly here - but ping me if you want to give it a test-run.
Love this - tried it. The problem as I see it is that these still require hosting - ideally (again, as I see it) self-hosting a script that monitors internal/homelab things also requires its own monitoring.
Short of paying for a service (which somewhat goes against the grain of trying to host all your own stuff), the closest I can come up with is relying on a service outside your network that has access to your network (via a tunnel/vpn).
Given a lot of my own networking set-up (DNS/Domains/Tunnels etc) are already managed via Cloudflare, I'm thinking that using some compute at that layer to provide a monitoring service. Probably something to throw next at my new LLM developer...
If anybody wants to be a clever clogs, combining both this and Uptime Kuma would be genius. What I want is redundancy. E.g., if something can't be reached, check on the other, likewise if one service takes a crap, continue monitoring via the other and sync up the histories once they're both back online.
This "local or cloud" false dichotomy makes no sense to me—a hybrid approach would be brilliant.
If anyone manages this, email me: me@hammyhavoc.com. I would love to hear about it.
Getting close to dark-launching a web-app that scans a domain for common issues - there's a heap of "performance measurement", "security analysis", "SEO scan" sites - but nothing that really does them all - a one-stop-shop if you will.
It's been a fun ride co-coding with Claude (Sonnet 3.5 > 3.7 > Code). Already it found a bunch of interesting bugs on a heap of my own sites, older employer sites, friend's sites.
Started as a simple Django web app, extended to Celery+Redis, now also leveraging CF Workers and R2 storage.
Was bourne out of an observation that some sites I have been working on missed some crucial things like domain expiration of asset-domains, mis-configured CORS or SSL certificates, http header and meta collisions, missing/wrong redirects for http/https/www/no-www etc.
There's a bunch, but most of it comes to the following:
1. Mis-matching declarations - e.g. a meta robots tag that conflicts with a HTTP Header x-robots-tag for example
2. Missing declarations - missing title tags, canonical tags, etc - not often critical - but not ideal either
3. Missing redirections from no-www/http - often overlooked
4. Open-graph images that 404
5. XML sitemaps that 404 or reference 404 resources
6. Mis-configured SSL/TLS headers
and more...
reply