I think you’re seeing the wrong causation when it comes to enshittification. FOSS licenses prevent that sort of thing from happening. Linux is already, by far and away, the most popular server OS so consumers moving to it isn’t going to make it worse.

I dunno, maybe be less of a hipster bestie?

SPH time!

It is when you use a private tracker and disable DHT, Local Peer Discovery and Peer Exchange.

Yeah it’s a little strange. Swift is Apple’s own programming language, and there was an older Jellyfin app on iOS that didn’t use it and so wasn’t fully “native” in a similar way to how most social media apps are just a web browser.

There is a native Apple TV app, I didn’t migrate from plex until there was and I migrated over 18 months ago. It’s called Swiftfin.

I’m not behind a CGNAT and that’s completely free. I do pay for that IP to be static though, but that’s only ~$6.50/month (USD).

Bingo. And if you don’t use apps with ads, like only using jellyfin, you get none at all.

Ah yep, found an article about it, it’s indeed disappointing behaviour on their part.

I still won’t support the pi foundation though.

Can I ask why? (/gen)

…I meant the keep watching thing. I get that a lot if I skip to the next episode right at the outro of a show.

Nah, I think that’s an issue with the jellyfin server. It happens to me too, using Swiftfin on AppleTV.

Rack server on a lack IKEA table.

Mikrotik make good hardware, what are you on about?

It does still have some issues, but it is being heavily worked on and has been for 12-18 months at this point. Has taken huge strides, and if you’re in the beta channel you’ll see lots of work being done.

There is, check out the Music Assistant add-on for Home Assistant.

The dev of this developed Caddy? Hmm… at least there’s talent behind it. I’m a little worried about creating that sort of record, but this guy seems earnest in wanting to liberate personal data.

The OS can’t get to the point of loading cpu microcode without that outdated, embedded microcode. The reason it can persist is because there aren’t a lot of good ways to see what that UEFI microcode actually is once it’s installed. Plus, only the UEFI tells you that it has successfully updated itself. There is no other more authoritative system to verify that against. So the virus could just lie and say it’s gone and you would never know. Hence needing to treat it as the worst case scenario, that it never leaves.

Hey, that’s really fair, thanks for being honest :)

Except that doesn’t at all explain the wider recall of 100 million units. Not every single one of those airbags were faulty. First of all, how could we know? Testing an airbag is a potentially dangerous thing to do, let alone on an enormous scale that would require under-qualified persons to run the tests. Secondly, it’s not a 100% failure rate. If it were, it would have been picked up far sooner than it would take to sell 100 million units. If it happened just as severely no matter the unit’s age, it would have been picked up during crash-testing. What actually happened was an analysis of statistical averages that showed a far higher rate of failure than there should have been.

The similarities to me come from a comparison to Schrödinger’s cat. In the airbag example, you don’t know if the unit in front of you is going yo fail until you “open the box” by crashing. With the AMD vulnerability, you don’t know if ur motherboard has been infected by any virus/worm/etc until a “crash” or other signs of suspicious behaviour.

In both cases, the solution to the vulnerability removes that uncertainty, allowing you to use the product to it’s original full extent.

Look at it this way, imagine if this vulnerability existed in the ECU/BCU of a self-driving capable car. At any point someone could bury a piece of code so deeply you can’t ever be sure it’s gone. Would you want to drive that car?

Sorry, I reread it and I understand now that you were referencing the AMD chip in a comparison. I guess I still would compare it most to the Takata airbag situation. You’re right that nothing happens on it’s own, but once you’ve “crashed the car” then it kind of is a lot like an airbag not going off. It infects your computer on a hardware level, and any future OS running off that motherboard is potentially vulnerable in a way that’s impossible to tell.