WxFisch

They can, I turned off my plex VM to save resources but no real reason they can’t both point to the same libraries at once.

So still not addressing the myriad problems the player has, especially on AppleTV where it’s been reported for nearly half a decade to not work well. But hey you get yet another place to do photos things (which they admit literally no one wants or uses, they’d be better off dropping support for photos altogether).

This is super frustrating because plex is very polished despite its clear bugs and misdirection. I just switched over to JellyFin and it’s faster and much more focused but just still has a lot of rough edges. I’m not sure which will be my long term solution but plex needs to attract folks to subscribe and focusing on features that 1/5 of a percent of users utilize is not how you do that.

The article title is misleading, but the research is interesting. Essentially it’s saying that when the rocket self-destructed due to it performing off nominal (as the first test ever of this vehicle) it ionized a large swath of the ionosphere from Mexico to the SE US which can impact the accuracy of GPS for systems that require high precision. The ionosphere reionizes very quickly naturally though so the effects are short lived (hours to maybe a day) and the impact to navigation at least should be small because of how GNSS works with built in corrections for exactly these types of errors. It feels like Nature is stretching a bit with the doom and gloom headline that the authors don’t even point to in the article (though I have not read the paper to be fair).

From my reading this is misleading at best and likely wrong. I don’t work with CrowdStrike Falcon but have installed and maintained very similar EDR tools in enterprise environments and the channel updates referenced are the modern version of definition updates for a classic AV engine. Being up to date is the entire point and so typically there are only global options to either grab those updates from the vendor or host them internally on a central server but you wouldn’t want to slow roll or stage those updates since that fundamentally reduces the protection from zero days and novel attacks that the product is specifically there to detect and stop. These are not engine updates in that they don’t change the code that is running, they give the code new information about what an attack will look like to allow it to detect malicious activity as soon as CrowdStrike knows what the IoCs look like.

In this case it appears that one of these updates pointed to a bad memory location which caused the engine to crash the OS, but it wasn’t a code update that did it (like a software patch). That should have been caught in QA checks prior to the channel update being pushed out, but it’s in CrowdStrikes interest to push these updates to all of their customers PCs as quickly as they can to allow detection of novel attacks.

For me as the driver of not one of these cars, I think the driver monitoring and sheeting is perhaps one of the most important parts of these systems. I 100% want your car to scream at you for not paying attention while use the driver assist features because it’s such a common and easy thing to do (if it works 99 times without issues, human nature is to assume it will work that 100th time, so checking that email from work real quick is probably fine). When the consequences of a driver failing to post attention while using these systems is potentially other people dying in a horrific crash, your discomfort at an alert because you happen to be a perfect driver that never does other things in the car while driving doesn’t matter.

I would recommend prowlarr instead of jackett for indexer management, and pihole as at least an additional blocking service but in reality it’s really all you need for use at home. I’d also strongly encourage use of a VPN on your *arr download services. I use a separate box to run Plex and then have my *arrs all running on their own VM inside if it to provide separation and allow be to more easily segregate the network traffic (as someone that doesn’t really know docker that well it “just works” for me. Also probably worth looking at how to store your media on an external target, it’s easy to quickly accumulate 10s of TBs of media and trying to store that all on the server locally is asking for trouble. Better to set everything up on a NAS to start.