DNS over TLS and similar are only encrypted to the first (local) DNS provider, and of course that provider knows the query as well.
It protects against 3rd-party eavesdroppers between you and your primary DNS provider, but does nothing for privacy beyond that.
Also getting rid of my T1 Diabetes and re-doing my transition, but yeah! Hedonism as well!
They blamed it on the communist party, yes. There were 8 parties represented in the Reichstag at the time though.
I am a bit confused tbh 😅
The link you send links to docker projects, the link I sent is the second one of those. Seems pretty straightforward?
But to be fair, I have never used docker for any of this. In my nix config, it's literally just:
services.prowlarr.enable = true;
services.prowlarr.openFirewall = true;
There's not really anything you need to configure host-side. Prowlarr needs to be able to communicate with sonarr and radarr (same as jackett), but otherwise it's basically stateless.
Spend the rest of my life on a Culture orbital or GSV? FUCK YEAH
Sorry to hear that that's been your experience! :( My installation has been running for ~5 years without any problems
Yeah no worries - I discovered Prowlarr from that exact same comment years ago so jumped at the opportunity to post it here 😆
Real question is, why Jackett instead of Prowlarr? 😄
Oh, agreed - I was just trying to engage with the hypothetical that "cool" was plastering all over this thread.
I have one big frustration with that: Your voice input has to be understood PERFECTLY by TTS.
If you have a "To Do" list, and speak "Add cooking to my To Do list", it will do it! But if the TTS system understood:
The system will say it couldn't find that list. Same for the names of your lights, asking for the time,..... and you have very little control over this.
HA Voice Assistant either needs to find a PERFECT match, or you need to be running a full-blown LLM as the backend, which honestly works even worse in many ways.
They recently added the option to use LLM as fallback only, but for most people's hardware, that means that a big chunk of requests take a suuuuuuuper long time to get a response.
I do not understand why there's no option to just use the most similar command upon an imperfect matching, through something like the Levenshtein Distance.
Not really, no