WxFisch

Kagi doesn’t hide that they use API calls to multiple sources for each search, they are fairly upfront about honestly. The benefits of use Jagi IME are the results are great, the site is fast and gets out of the way, it’s fairly affordable for what it provides, and the goals of the company is in line with mine (namely to find a thing I’m searching for). They are well funded enough to give me confidence that I’m not going to have to configure yet another search engine, and the integrate into pretty much all my access points easily as a default search engine.

I have seen no reason to think they abuse their position to impact my privacy, and bring closed source does not automatically make them evil. You included no alternatives that are open source, and the ones I explored were either difficult to get setup, required me to run something on my own infrastructure, or didn’t provide the integrations or results I expect. Kagi does.

Kagi isn’t perfect, and there are a ton of suggestions on their feature tracker that users rightly want implemented (including open sourcing more of their code-base). But as a paid search engine that makes me not the product, it does that job well.

Looks from the article like it was stolen by infecting the PC of a third party analytics firm user who had privileged access to Hot Topics snowflake data warehouses and didn’t have MFA enabled. That is just inexcusable in this day and age and $100k is a small price for Hot Topics snowflake to pay for that fuck up (assuming the bad actor actually follows through and doesn’t sell the data if HT pays the price set). Pro tip (or really amateur tip), MFA all the things. Even SMS based MFA is better than no MFA even though it’s not ideal.

No, because no one intends to hit a pedestrian with the car they are buying. That’s why we need to mandate safer vehicles, not trust people to factor that in as they look for a car.

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.

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.

In most companies I’ve worked for, T1 is there to put in tickets from calls, and handle the simplest of tasks (password resets, account lockouts, “have you tried turning it off and on again” tasks). Anything beyond that is generally sent to T2 (usually the desktop team who then force other teams to accept tickets as needed) and T3 for anything that more systemic or needs deeper troubleshooting and system knowledge.

In many places it’s a combination of piss poor pay creating little motivation and high turnover (and thus lack of training) and management prioritizing the wrong metrics (generally looking for short call times and short call queues). If you want to try and improve things I’d suggest learning about the KPIs that team is expected to meet, and then ask management why they chose those metrics. Generally I’ve found prioritizing first call resolution over call times to be a huge improvement to motivation of the team and user satisfaction scores (we all like solving problems and users tend to be way nicer when you fix the issue vice kick the can).

I would say, at least to your point about them not having access to systems, that’s it’s very common for T1 to have pretty limited admin access to systems. Partly to protect against inexperience, but also as a social engineering protection. If they need to ask for access to pass a ticket for elevated rights, it gets another set of eyes on the call to ensure it’s all kosher.