Why would I hike 10 miles with you?
Why would you even compare "normal walking pace" to an FPS?
Beyond that, 3-4 seconds for a 360 at a casual pace is still ridiculously absurd. I'd say anything over 1.5 seconds indicates either obesity, octogeneriacity, or some other sort of disability.
I was referring to shitty FOVs for console games, not absurd fisheye Quake shit. A correct field of view can be determined based on the display and distance. You won't get motion sickness from a wide FOV if you just set the FOV correctly.
And your inner ear takes a back seat to your vision. Your brain will quickly ignore your inner ear if it's not matching what you're seeing unless you have a medical condition. This is why the spinning tunnel illusion works (http://vortextunnel.com/). This is why it's difficult to stand still with your eyes closed. This is why the VR demos have shit like walking across a high beam. This is why when you're dizzy from spinning around 10 times with your head down on a baseball bat at the company picnic, you should focus on the guy in the outfield to steady yourself, not the ball on the tee a few feet in front of you. The more your vision mismatches what your inner ear says, the more quickly your brain stops listening to your inner ear.
When your inner ear is overriding your vision for whatever reason, you get a condition known as vertigo. If your inner ear is working normally and you have vertigo, you get a little dizzy whenever that fluid sloshes around. If your inner ear is fucked up due to infection or whatever and it's sending you bad data, you get debilitating loss of balance, motion sickness, etc.

3-4 seconds? Is that 1 second per hundred pounds?

That's because console games almost always have a terrible field of view. PC games are more likely to have a wider field of view and are more likely to let you adjust it.

Fingers? Those are dildos. Rig this up to a cock and you'll have an actual use case.
But as it stands it looks completely useless.

My KeePass database won't be cracked unless someone breaks AES.
If my PC gets hacked and I use KeePass, I'm boned for every password I have. Without KeePass, I'm boned for every password I use while hacked.
If my shit is hacked and I'm typing in passwords, that means I don't know my shit is hacked, so I'll be typing in passwords with reckless abandon.
With KeePass, I at least have a list of all passwords I need to change once I figure out I've been hacked.

XKCD is terrible, as usual. 4 dictionary words has low, low fucking entropy.
95% of all English is done with less than 5000 words. Most people only ever use a fraction of that. When tasked with coming up with a "random" selection of words, most people will use an even smaller fraction. Your 5000 word bank is going to be closer to 500 once you task a human with thinking them up. And they're going to be mostly nouns and adjectives. And when you task the same human to come up with a new set they're going to pick the same words.
Instead of 5000^4 you're looking at 500^4 or 1000^4 if you're lucky. And then of course most systems will simply truncate your password if it exceeds a certain length. Just a few years ago most sites simply truncated anything beyond 8 characters.

A typical keyboard will have 94 different characters ignoring whitespace, though many systems will reject a handful of them.
Consider even just a 64-character set [a-zA-Z0-9!?]: 64^6 > 500^4, 64^7 > 1000^4, and 64^9 > 5000^4.
Using an 80-character set means an 8 character password beats 5000^4.

Users should be generating random passwords using a full 94-character set. They should only dumb that set down if the site rejects certain characters. (The easiest thing to do is to just generate a new password and try again.) These passwords should be at least 8 characters long, though ideally they should be as long as the site allows.

But users won't do that unless it's easy for them. So why not use javascript to have the user's machine automatically generate a suggested, random password using the full character set your site allows, while meeting your complexity and length requirements? On the registration page you have an area that shows the suggested password with a "regenerate" button the user can click to churn through a few of them if they want. Then make the user type that password in twice, as usual. This introduces no security issues as long as you don't host user-generated content (XSS) on the registration page.

The only problem is the typical issue of people forgetting their passwords. They can do the same things they've always done - remember a few and reuse them, write them down on paper and hide that piece of paper, or forget them and reset them as needed.
Having to reset your password(s) when you forget them is an inconvenience, not a risk.
Using good passwords means that when a site gets hacked you don't have to worry/hurry as much (assuming they didn't store them in plain text and didn't use MD5 or some shit).
Writing passwords down and hiding the paper at home is a minor risk. Leaving a post-it with the password on your monitor at work is a moderate risk. Using shitty passwords is a major fucking risk.

Telling people to use shitty passwords so they can remember them is the wrong fucking thing to do. The fact that the passwords you suggest are shitty in a different way doesn't change that fact.

KeePass. It has strong encryption options, it isn't tied to any site or service, the (encrypted) database can be synced however you want (such as with Dropbox) and used on any devices you want (including phones), it's got all sorts of options for generating passwords, automatically typing them, automatically expiring them, etc., and it's fairly light weight.

I'd pay several moneys to see Thor with Parkinson's disease wield Mjolnir.

Thor is a male god.
Thor is an established character, based on the mythical Thor.
Making Thor female is just a publicity stunt.
Marvel can't create compelling original female characters, but that doesn't mean they should slap tits and a vagina onto existing male characters and hope they stick. What Marvel needs to do is realize that they can't create ANY compelling characters anymore, male or female, and fix that problem first.
Everyone knows that the real Thor will be back once this "arc" finishes - saying something is permanent in comics is an insult to anyone who reads them.

Alternatively, Han shot second.

I don't know many corporations with standing armies, navies, air forces, space exploration programs, nuclear arsenals, etc.

We really should be recognizing him as the clown he was, and recognizing the administration and the cops and the courts as the tyrants the continue to be.
Instead he's been propped up as some sort of tragic hero figure and attached to things that have very little to do with him or the case against him, and thus the important shit (the tyranny) gets lost in the haze.

He made 3 statements.

Why do people get shingles decades after having had chicken pox?

They let their buddies into the group and exclude others.
Their buddies get free access to patents, everyone else has to pay.
Antitrust says anticompetitive shit like that is illegal.

This is a clear cut instance of collusion.
They should be forced to continue to defend their patents or to release the patents to everyone on the same terms.
Patent groups, from this shit to MPEG to BluRay to whatever, destroy innovation more than any individual patents do.