-
Home Assistant
:house_with_garden: Open source home automation that puts local control and privacy first.
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
-
keepassxc
KeePassXC is a cross-platform community-driven port of the Windows application “Keepass Password Safe”.
-
community
Discontinued This repository holds the content submitted to https://cloud.google.com/community. Files added to the tutorials/ directory will appear at https://cloud.google.com/community/tutorials. (by GoogleCloudPlatform)
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
The author mentioned they would be moving towards local smart-home solution but doesn’t mention HomeAssistant even once
https://www.home-assistant.io/
On Android you can install https://newpipe.net and turn off a lot of things (no more trending/start screen recommendations, you can turn off comments, or "watch next" recommendations.. the shorts show up in the search results like other normal videos, with a slider so you can still navigate it.
There is a pull request for adding passkeys to KeePassXC:
https://github.com/keepassxreboot/keepassxc/pull/8825
GKE is an abomination. Its reputation is completely undeserved. Sure there's some nice things out of the box, like authenticating to clusters with your Google/GCP account, but day 2 operations are a constant frustration.
What sucks?
1. The Kubernetes Pod garbage collector is configured to be abominally slow, keeping terminated pods in the API server for far too long. This interferes with cluster monitoring by making it seem like there's a consistently high number of OOMKilled etc. pods rather than blipping as it happens. GCP support claims this is working as intended and recommends manually running a script to clean up the API server if it bothers you (this is a managed service?!). See e.g. https://stackoverflow.com/questions/75374590/why-kubernetes-... .
2. The rest of the Kubernetes world moved on from kube-dns and on to CoreDNS. Not GKE! On GKE your two options are kube-dns and the GCP VPC-native Cloud DNS (i.e. Kubernetes service and pod records are listed in the private DNS zone for the VPC). Surprise surprise - if you pick Cloud DNS to help scale your cluster, because GCP isn't operating kube-dns well enough on its managed control plan, then you're on the hook for paying for the Cloud DNS zone as well, it's not included in the GKE cluster costs. See e.g. https://cloud.google.com/kubernetes-engine/docs/how-to/cloud... .
3. GKE clusters automatically log to GCP Cloud Logging, the first 50 GB of which is free. Fair enough. But the price afterwards is a truly mind-boggling $0.50/GB! (https://cloud.google.com/logging/#section-7). How do you turn off GCP Cloud Logging so that you can ship your logs to a cheaper vendor instead? Nope, there's no first-class managed setting; all you get is a community tutorial (https://cloud.google.com/community/tutorials/kubernetes-engi...) that links to this GitHub configuration (https://github.com/GoogleCloudPlatform/community/blob/master...) aaaaand good luck :)
4. No native IPv6. See e.g. https://stackoverflow.com/questions/64110542/has-anyone-iden... . AWS of course does support IPv6: https://docs.aws.amazon.com/eks/latest/userguide/cni-ipv6.ht...
For me it's metrics.
We have a heat pump, so we change the temperature roughly twice a year: heating temperature in winter, air conditioning temperature in summer.
But my Ecobee reports the temperature in three rooms (and occupancy, which I tie into automating lights), outside temperature, outside and inside humidity, fan/heat/cool start/stop times, and some other more obscure metrics up to the mothership, and the excellent third-party website Beestat[1] tracks all of those using Ecobee's well-documented API. It lets me spot anomalies, and helps me understand if I've got the resistive heating configured to come on at the best time.
If we had time-of-day rates for electricity, it would optimize for those, but we don't have time-of-day-rates.
(If I had gas heat, or if I didn't work from home, I'd at least schedule temperature changes to set things cooler at night or when we're away -- maybe driven by the occupancy sensors! -- but apparently that's not effective with heat pumps.
[1] https://beestat.io/