Minnesota's has expansive rivers feeding the Mississippi[1] and it has one million acres designated to a canoe wilderness -- the Boundary Waters Canoe Area Wilderness -- bounded by the Canadian Quetico to the north[2].
They are navigable by canoe by design, yet they are flitting dots.
It gives me pause; what is this site trying to convey? It's a fantastic effort, yet for the water we have, it doesn't match.
This is captured in the Layers of Time diagram[1]. The tension fashion to nature is at diametric odds with time and responsibility; governance is squarely inbetwixt.
Ctrl-C escapes insert mode, and does not check for abbreviations. It has a different behavior.
<Esc> or CTRL-[ End insert or Replace mode, go back to Normal mode. Finish
abbreviation.
Note: If your <Esc> key is hard to hit on your keyboard, train
yourself to use CTRL-[.
If Esc doesn't work and you are using a Mac, try CTRL-Esc.
Or disable Listening under Accessibility preferences.
i_CTRL-C
CTRL-C Quit insert mode, go back to Normal mode. Do not check for
abbreviations. Does not trigger the InsertLeave autocommand
event.
You can use a YubiKey for a portion of a master password. This is best used by manually typing "correct" and autocompleting the latter portion with plenty of entryop of the password/phrase "battery horse staple" from the key. This way, if someone steals the key, you've still got a secret.
You'll still need a password manager to store the unique passwords for your services.
In 2005, Bruce Schneier noted the purpose is to provide a fallback password[1] if the primary password was forgotten, but the reality is, security questions are a much less secure protocol than passwords themselves.
While on a personal level you can fix this by using a password manager and generating another random string as an answer, other cute and terrible implementations like United[2] (calling you guys out) obliterate it, making yet another, terrible, horrible, no-good secondary protocol.
Why companies use them is because the Powers That Be(TM) believe it to be a secure protocol. They localize the problem to themselves and since they haven't been exposed using their mother's maiden name, it's good enough. Also, everybody else uses security questions, even our competitors, so we have to be at least as secure as them, right? The key phrase is "at least". Then you are equivalent in policy and protocol; certainly not more secure. :D
Joking aside, not a bad bet.