• 2 Posts
  • 228 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle






  • The one mechanic is similar, yes. But the gameplay and exploration are drastically different.

    I can’t praise the game enough… it’s just so good.

    For example. You’re in a dungeon and then it happens and you go back.

    In some ways something happens when you’re pulling on some thread. There’s no dungeons, no goal (explicitly). You are exploring and as you learn more you realize there’s areas to check out because they’ll answer some question you have about what happened or why something is the way it is.

    In this case perhaps the mechanic occurs and you find yourself briefly annoyed. But then you go back to the spot, this time things are in a different place and state and you realize something happens that allows you to go further which leads to another thread/mystery.

    And then you’re off. As time goes on you learn to accept and then even invite it. More and more you unravel deeper mysteries, learning what and why and then seeing earlier conclusions in a new light.

    Why it’s happening, how it’s happening, what can be done and can’t, etc. it’s really a one of a kind experience.













  • The hassle and delay is part of how it works. If there was a seamless catch all then it wouldn’t be feasible to make it secure.

    Having a second physical factor, as much as it can be a hassle, is much better than any single factor.

    Your password can be breached, brute forced, bypassed if there’s an issue somewhere.

    Your biometrics can’t be changed so anything that breaks them (such as the breach of finger prints in databases, etc) makes them moot.

    A single physical token can be stolen and/or potentially cloned by some attack in physical proximity (or breach of an upstream certificate authority)

    But doing multiple of those at the same time. That’s inordinately much harder to do.

    I will say the point/gist of the article is a good one. The variety of types some used here and others used there does make it a hassle to try to wrangle all the various accounts/logins. Especially in their corporate and managed deployment which isn’t saving passwords and has a explicit expiration of credential cache (all good things)