• 1 Post
  • 12 Comments
Joined 2 years ago
cake
Cake day: January 13th, 2024

help-circle




  • Just because something is popular does not mean you will like it. Different tastes and all that.

    As for me, more variety means more reach to gamers out there. What I don’t like to see is stagnation for years on established IP to the point is becomes boring (for me personally, Pokémon falls a lot into this category for most releases. The only Pokémon game I liked recently was arceus, simply because the whole battle and catch system got revamped to be something different for once)







  • It’s a high paced fps in general. The original mode is semi roguelite, meaning, you have to go every 10 floors in order to get a checkpoint. If you don’t, back to the previous checkpoint and get different perks for the run.

    For me the whole cyberpunk esque thing about it sold me. And is also a quite unusual sort of shooter.

    Only a tad short, that is my biggest complaint (but price does match the time so I can’t say much)



  • So what you want to do, effectively, is to have different security requirements for different accounts. Correct? And all in the same file.

    For now I just want to get a few things out of the way:

    • with this strategy, what are you protecting against?
    • how likely is this to happen?
    • what is your contingency plan?

    I believe its good to have different levels of security for different things, but you also have to understand at what cost you need it.

    I can propose a different thing altogether: for the very important passwords, like banks and such, use the pepper method. This means, you have on your password manager part of your password, and a small portion is something you know. Example: generate a 25 chars password, and have at the beginning or end, more 5 chars that you know (can be letters and numbers, and can be something you remember every day, like the first letters of your address plus house number).

    With this approach, there are a couple of benefits:

    • you can still have computacionaly heavy passwords
    • if an attacker gets a hold of your open vault and try to login, it will fail since the password is effectively not complete

    Biggest downside I see is remembering the pepper always. And make sure is not written anywhere. And of course, yo can always argue it is possible at some point to get the correct password with the base password known. But at this point, thus should give you enough time to change it and thwart the attack. Remember: there is no perfect security solution, only sufficiently good ones that can be usable and effective.