I mean, bugs are a part of all software. Stability is about reliability. That if you boot up your computer you are less likely to spend the first hour or two troubleshooting unless you just did a major upgrade. I'm not saying Arch is unstable, just less stable.

Apple hardware is good, but not priced at the same quality to price ratio because there's no competition. You can get other brands with higher quality at the same price point that better supported by Linux.

I think that was the point there. Not that Apple has bad hardware, but lack of competition and the premium for the product family mean you can get higher specs per dollar with many other manufacturers and you can find hardware that won't require "jailbreaking" or other workarounds or missing drivers to get it working with Linux.

Sounds like this might be specific to your brand of TV. I have a Sony and there's a bunch of Sony junk on there that I disabled a long time ago. But my TV app doesn't have any ads in it yet. I'm guessing your manufacturer added ads to their TV app and made a deal with Google to use them as the ad provider. Unfortunately, those apps are relatively proprietary since they are supposed to be primarily just a simple UI for the tuners and so mostly hardware specific. Not saying there aren't replacements, but likely that would require someone to reverse engineer some of of the hardware firmware's APIs rather than web APIs that most apps interface with and aren't guaranteed to be the same across models. Those are only available if you own an actual TV, so it's less likely to exist.

Anyway, my point is that your searching probably needs to focus on the TV rather than the Android/Google TV platform as a whole. Look on forums devoted to the TV brand. You may have more luck.

The other alternative might be to block the ads on your router, but that may or may not work or cause some unintended inconveniences. For example I have Google's DNS blocked and my wifi constantly drops and reconnects even when I only want to watch locally hosted content because the TV thinks it's offline and needs to fix the connection.

I have it set up with "only not embedded" and then I let the preview load and click on the YouTube link to make it pop out and it redirects to Invidious and works. Not directly watching it embedded, but it works well enough for me. I just tested this site on my phone and it worked. Should work on desktop similarly. Just with this you have to get to the point where it loads the preview of the video at least, so you can click to open it outside of the embed.

I use librewolf on desktop and IronWolf on mobile with the libredirect plugin. And I have a pihole that does ad blocking, so eventhough I don't have YouTube totally blocked, it refuses to play even with a wide open browser.

I've never gotten the embedded option to work, but Google is constantly fighting Invidious, and pop-out is a minor inconvenience for me.

They're just the only ones who got caught. Giving that kind of access to almost any corporation or government agency without oversight is going to result in them targetting people who are critical of them. The data should not exist.

Two issues I have:

1. There is a license on what you can install on the device. Open means no licenses on owned things, regardless of how open that license is initially, it can be changed.
2. The server it connects to is not configurable. You have to build your own firmware and maintain it and that goes back to the first point in case they decide to change the license.

Problem for me is that there is some kind of restriction on accessing the device's API at all and you pay extra for the key that will get created when you unlock it. This may mean that some kind of lock is in place on the device that has to have a key for it created. Even if they give you a key, what happens if an update removes that key's validity, even unintentionally. I've had this happen with products in the past. A bug will restrict access to things or worst case, will totally brick the device because the lock is stuck in place.

Not saying this device has that problem, but the concept of a lock existing means it could intentionally for profit, maliciously by hacking, or unintentionally end up locked later, so I'm just against the concept in the first place. It's a potential point of failure for no good reason but profit on a device that is supposed to be open. I'd happily accept if they changed a little extra for a device that had no lock at all. Just I don't want a device with a lock on it.

Also, I'm not sure how having my own server helps here, in fact that's my plan in the first place as I want to get the thing to interface with my own internal systems. Maybe I'm misunderstanding the implementation, but my understanding from the very brief information available is that you get on your device, connect to their server to pay a fee, and then a key is created for you and then you can access the endpoints running on the device either through the server or directly with REST calls. The alternative is to teardown the device and build your own custom firmware that uses different authentication mechanisms. I don't really have the interest to mod the firmware and then have to maintain a fork for getting official updates. I just want to be able to be able to interface any servers I have with the device as I choose.

Thanks for the correction, that was a typo based on a long work day screwing with my brain processing acronyms. I meant to say DNS over TLS or DNS over HTTPS.

No. I don't use DoH inside my network because I redirect DNS traffic on my primary VLAN to a pihole for ad and malware reducing. But I also control what has access to that VLAN pretty strictly. I have another VLAN for guests and untrusted devices that doesn't use the redirecting, but does use the Unbound server as the default DNS, just doesn't enforce it. And I have an even more locked down VLAN for self-hosted servers that also doesn't use the pihole, but does use Unbound.

Yeah, the system was on a single server at first and eventually expanded to either a docker swarm or Kubernetes cluster. So the single server acts as both a docker host and an NFS server.

I've had this happen multiple times, so I use this pattern by default. Mostly these are volumes with just config files and other small stuff that it's OK if it's duplicated in the docker cache. If it is something like large image caches or videos or other volumes that I know will end up very large then I probably would have started with storage off the server in the beginning. It saves a significant amount of time to not have to reconfigure everything as it expands if I just have a template that I use from the start.

Reduce space used by cars and give it to the robots. Increase funding for public transportation to compensate. Overall, this will improve lots of things and the problem is being caused by corporations, not pedestrians, so if people don't like "giving up their cars", then they can complain to the corporations instead of complaining to the cities.

Yeah, probably best bet is to uninstall and purge settings. Depending on the district you're using and it's package manager, you it may be as simple as apt purge vim. And just to be sure remove all vimrc files from all user home folders including root.