kinda just figuring out lemmy so here’s a dumb meme

reddit jank actually meant I couldn’t delete my account when I logged onto it, so… thanks?

on the downside I think I may have lost my

spoiler

archlinux femboy x gentoo gf

stuff as a result, but I can just draw it better ig.

    • emmowo@lemmy.worldOP
      link
      fedilink
      arrow-up
      7
      ·
      edit-2
      3 days ago

      for once this is just me reverting back to caveman brain where i just do > char + 64 and char + 96 tests so I can avoid stdlib on C… (which is really dumb)

  • Buffalox@lemmy.world
    link
    fedilink
    arrow-up
    8
    ·
    edit-2
    3 days ago

    Ultimate indeed, it doesn’t get more secure or accurate than that!
    You have single handedly solved the problem of age verification, congratulations!
    Time to patent and monetize. 💰💰💰

  • palordrolap@fedia.io
    link
    fedilink
    arrow-up
    2
    ·
    3 days ago

    I see at least a couple of problems here. The main one is that it assumes that the computer only has one user. This is often true, but not always.

    Yes, I know it's a joke, but if you really must, read on...

    If this script is run by a child on a shared computer, and that child chooses not to lie, the child and all adults with access to the machine lose access to /sbin/doas. Likewise if one adult chooses to lie that they’re a child, they’ll lock themselves and everyone else out, child or not, which is an opportunity for malicious behaviour

    It also means that something else would need to be done with regard to /etc/enviroment. Even on a one user, two roles machine, that entry really ought to be under /etc/environment.d, but the more robust, multi-age, multi-user solution would need something entirely different to be implemented. /etc/profile would be the wrong place, and editing each user’s .profile (or equivalent) and then making it read-only seems like a bad plan too.

    • emmowo@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      2 days ago

      if we are being kinda serious, we would probably just go with either the systemd user metadata solution, or… (on a scale of insane to less insane):

      • store it in a passwd comment (which means the finger command will now remotely leak age, but is backwards-compatible)

      • have an SELinux (or similar) setup so that new users have more restricted permissions by default. While I would absolutely do this myself whenever I have kids, this is just really unnecessary for most everyday users. At the very least this obfuscates the reason why a user might have less permissions.

      • make a generic, encrypted-by-owner file in /etc/, but this still has privacy issues if we need every account to state their age.

      Obviously the best solution is just educating parents about managing parental controls, but we can’t have nice things ig.