Flatfire

If I’m remembering right, RHEL is Crowdstrike’s primary Linux target. And NixOS wouldn’t even be a factor since it’s basically just not enterprise grade.

That said, they need a serious revision of their QA processes.

What are you, an apostle? Lol. This issue affects Windows, but it’s not a Windows issue. It’s wholly on CrowdStrike for a malformed driver update. This could happen to Linux just as easily given how CS operates. I like Linux too, but this isn’t the battle.

No problem, glad I could help!

Arm64 is generally appropriate for most modern phones. Armeapi is targeted at 32-bit arm devices. These are uncommon these days. X86 is rarely used with Android devices, since it’s broadly unsupported.

Of course Universal is as described, and should work if you’re still unsure.

Imo, plugins should have separate config files, with uniform, consistent formatting. Separating them ensures that plugins never modify primary configuration details, they can be updated independently, or deprecated without affecting future functionality. It also means you can take regular and reliable backups of each config.

Depending on the developer, and the scale of their game, these things can also be incredible cheap to produce too. If your gameplay/monetary loop is something designed to arbitrarily force a player to wait to accomplish something or otherwise spend money, then you can drastically reduce the amount of content that needs to be added as long as you have an adequate base.

Even if you spend money, loot box mechanics and randomized stats can push players to continue to spend because while they got an item, they didn’t get the perfect item. Base builders, team combat titles and character based games are very, very effective at this.

For developers like the one behind Evony, they can be a lot cheaper because that game, and a hundreds like it have existed all the way back as far as farmville and earlier. They just got better at the monetization loop over time.

Similarly, if you’re born at the tail end of Millenial/start of Gen Z, then you still grew up with a collage of 90s and 00s culture and inconography, offsetting the definitions the groups typically gain over time. Some Gen Z grew up into adolescence without really feeling the advent of the modern internet or social media. The end of that range never knew a world without it.

Generations are useful statistical groupings, but don’t represent individual experiences or influences, leading to disparity or outliers that feel excluded from their “peers” so to speak. I’d say I probably share more experiences with Gen Z, but a lot of the cultural aspects of my childhood are closely linked to later Millenial ones. There’s a gradient, not a cutoff.

With that in mind, a battery health tool is probably the fastest way to tell how old a phone is going to feel. Otherwise nothing else is going to suffer wear and tear. If the phone is in good shape, and the specs are agreeable, then it doesn’t matter how old it is.

Hey there, I’m not sure I understand what you mean by “first activated”. In general, you activate a SIM card, not a phone. This would be associated with your current phone plan, not the device itself. Your carrier would be able to provide that info. If you’re referring to when your phone was first purchased/turned on, then most folks tend to add their Google account during setup, which might be why there’s a suggestion to check your Google account to see when the device was added.

The IMEI is potentially useful as it’s a device identifier, but generally doesn’t matter to anyone except your carrier.

Absolutely. Android devices are dirt cheap, and ubiquitous in most of the world. It’s an obvious choice for many based on that alone. There’s also lots of families that aren’t in Apple’s ecosystem.