I have a couple ShieldTVs (AndroidTV) that have worked for me for years. They have worked with streaming services as I needed, but the main use case for me is Jellyfin for movies/tv and a good YouTube client that filters ads out. The shield has done a good job of passing the correct audio stream to the receiver and it looks good. There have been a few issues here or there with some codecs, but if I fall back on Kodi it usually works.

I haven’t tried an AppleTV despite being a mostly Mac/iOS household. It is difficult to find out how well the Jellyfin clients work on it, and last I checked there was no “official” client, just pay-for apps that may or may not do what I need.

I have something similar it’s been working great.

I have been thinking of trying to set up a “router on a stick” as a live backup but once I started researching it, it got daunting.

There is the old adage “Nobody got fired for going with Microsoft”, and it is real.

If you, as an IT guy recommend Linux, and some exec has a problem with his laptop (which they would have had no matter what OS is running on it) it WILL be your fault because you changed something.

My main workhorse VM is Ubuntu LTS because when I set it up I just picked it instead of spending another week researching and trying different distros. I could look into swapping it out but nothing has annoyed me about it once I figured out to disable snaps.

It feels like every time I finally have something set up and running I find some article telling me that what I chose is dumb for reason xyz and I really should be using something different, but refactoring at this point is a pita so why mess with something that isn’t broken?

That article was interesting but such a pain to read. Every other paragraph was repeating itself. I miss editors.

I found this comment on what happened by dani-garcia, one of the main devs:

The short version is that around 8-ish years ago, Bitwarden changed the way the vault items were structured, and Vaultwarden added some backwards compatibility fields to ensure both old and new versions of the clients worked.

These backwards compatibility fields were supposed to be a temporary measure, but for at least the next three years the clients still required them, until we eventually forgot to keep track of them. At some point between 2021 and today, the clients stopped requiring these backwards compatibility fields, but Vaultwarden was still sending them.

This wasn’t a problem until Bitwarden decided to use the backwards compatibility fields in a completely different way, which caused the clients to crash.

Found here: https://github.com/dani-garcia/vaultwarden/discussions/7473

I like these posts, I feel like there are many levels to any self hosted setup and getting an idea of what everyone is doing is fun.

This is a problem with more than just Microsoft. Any software (game, application, library, whatever) that has had many years of updates some of which are breaking, will have this problem with docs.

Oh you are using version 5.5.24 of xyzlib? All these docs are a mixture of stuff when 4.2.57 was out and stuff someone tried to update when 7.5.14 released.