Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Well that leaves me with mixed feelings.
Thread itself doesn't need Internet connectivity, but thread seems to almost always be paired with matter, which does (during provisioning).
I like that matter provisioning requires verification of their certificate, but I don't like that certificates can expire or the certificate authority can shut down. Although maybe that's all taken care of by the DCL? In which case that'd be fine.
In theory, Home Assistant could also give users the option to ignore certificate checks.
I also haven't seen specific details on whether Home Assistant's implementation allows sensors to contact the internet by default or what setting changes this.
It's just foggier and less user focused by design in my opinion. But as one would expect when Google and other large corporations were the ones to develop it,
It's also pretty obnoxious that it requires an Android phone with Google play services enabled (and even a Google login IIRC) or an iOS phone. There are ways around this, but they are pretty complex and not well documented.
My understanding is that that is because Google and Apple want to onboard it to their own home automation platforms, and HomeAssistant just piggybacked on that because it was easier, and it hasn't been a priority to rewrite it. But this is based on a few old threads I just looked up, I'm not exactly an expert.
I think there was some talk about Bluetooth onboarding, but that'd require the devices to have a Bluetooth radio, which is more expensive that a QR code sticker. Idk if anyone uses it.
Having something like a WEP button would certainly be nice though.