• 0 Posts
  • 86 Comments
Joined 11 months ago
cake
Cake day: September 15th, 2025

help-circle




  • I know this is a Linux community and therefore we love to hate on Windows…

    but for anyone that hasn’t used Windows in a while, they actually finally implemented relatively decent package manager in the form of “winget”. When you add the wonderful UniGetUI on top of it you get a pretty good experience.

    It had issues early on with consistency but the last ~year or two has seen it get a ton of improvement. It’s much more reliable than it used to be.

    Obviously “it’s about goddamn time” and it doesn’t hold a candle to mature package manager like what’s available on Linux.

    But if you’ve not experienced it before, and are forced to use Windows sometimes, it’s worth checking out.



  • The only real “emergency” I can think of is when I saw someone get hit by car while trying to run across a three-lane road. Went over the hood. probably a 30MPH hit

    The driver sped off. I pulled into the middle (turning) lane, put my hazard lights on, and tried to help the person. They were unconscious at first and then extremely dazed. Some other bystanders tried to get them to “walk it off” but I demanded they stay still and not move their head or neck until paramedics arrived.

    Fortunately a nurse saw it from their apartment balcony and rushed out to help. They obviously agreed the person shouldn’t move.

    Kind of wild looking back that so many people wanted this person who just got laid out by a car to pretend like they were completely okay. So fucking dangerous in that situation.


  • The analogy is perfectly accurate.

    An imperfect, simpler form of security vs a higher, more cumbersome form of security.

    Where is the problem with that analogy?

    Biometrics are not “bad practice for anyone concerned about security”. They are one type of security that is sufficient and effective for certain risk profiles but not others. Users should make informed decisions based on their needs and the features of the security implementations they are considering.

    Your hyperbole is, in fact, dangerous as it pushes people who do not understand security to blindly accept policies that are not good for their risk profile. We have proof that proper usage of biometrics is more consistent with end-users than proper usage of passwords. It’s not just about convenience. It’s also about adoption and proper compliance.

    Absolutist policies and positions like yours do harm. Just look at how NIST recommendations have moved away from things like frequent password change enforcement because it leads to bad behavior (writing down passwords, etc)




  • This has big “don’t use a standard deadbolt on your front door; it’s not as strong as reinforced titanium doors with time-release locks” energy

    Like, not technically wrong, but does not fit the standard risk profile, it’s overkill for most situations.

    Also to everyone talking about US law enforcement, this is just so easy to protect from, not worth ditching biometrics: if you see cops approaching and are worried about a device being unlocked, just reboot it. If you need to do it surreptitiously, just hold the power button to force shut it off after ~10s. This will always require a password to unlock after


  • As someone who works in this problem space, I promise you with 100% certainty that the type and quantity of data collection being done without kernel access would be far more distasteful than what’s done with kernel access. You can take my word for that or not but I obviously can’t say any more than that

    Including cheating functionality in games is already done and people hate it: it’s called pay-to-win microtransactions.

    The archetypes for cheaters are such that they don’t provide ways to please the a large portion of cheaters without harming players because harm is their goal. And the other group is trying to make money by charging for services for players and then cheating to complete those services as fast as possible. There are no in-game features that can be created to mitigate these people.

    The only class of cheaters that can be dealt with as a service problem are those that are cheating to a) catch up to others or b) offset a skill shortfall or c) offset a time shortfall. This makes up only a subset of an cheaters



  • I want you to know that I literally work in this space and you are handwaving away an incredibly complex problem space that hundreds of smart people have been trying to solve for decades now and it’s only getting harder (good cheat suites use hypervisor mods and direct memory access kits these days). I would love to educate this community but I’m under NDA (in addition to not wanting to provide information that attackers can use to better understand how we approach this problem space)


  • I want you to know that I literally work in this space and you are handwaving away an incredibly complex problem space that hundreds of smart people have been trying to solve for decades now and it’s only getting harder (good cheat suites use hypervisor mods and direct memory access kits these days). I would love to educate this community but I’m under NDA (in addition to not wanting to provide information that attackers can use to better understand how we approach this problem space)



  • Are you a videogame networking engineer? Because you’ve just handwaved away one of the most difficult challenges in gaming as if it were “duh that’s easy” level simple.

    I can link you some GDC videos that talk about how hard this problem is if you want

    ETA: Also you’ve only addressed memory modification attacks. This does not address external aimbots that read memory to determine enemy player position and then send legitimate-but-automated inputs to aim and shoot. How do you stop cheaters from doing this when they can see exactly how data is structured in memory, how values are obfuscated, etc?