1Password supports saving the 2FA token: https://support.1password.com/one-time-passwords/. Though you could argue that's not much safer than not using 2FA since if 1Password is breached, the tokens would be available as well.
As an alternative, you could use Authy, which backs up the tokens encrypted (just don't store the Authy password in 1Password if you're worried about that being a single point of failure).
The other aspect of this is that the crows could become reliant on this mechanism as a food source and be unable to survive on their own once it is removed from the environment (or runs out of food).
> So today, after almost 6 months of extensive testing, we are enabling zero latency typing as the default setting in all IntelliJ-based IDEs, including CLion.
At https://vline.com we provide a free WebRTC-based video chat service. It doesn't require any registration or installs and is built on top of our developer platform: https://vline.com/developer/.
We used that to build GitTogether (https://gittogether.com), which is a similar concept to this: text chat and video chat with people you follow plus members of your teams and organizations.
At vLine (https://vline.com) we often work remotely (or from home) and use that as a way to dogfood our service. We just set up a "vLine link" to a TV in our office and people can jump in and out throughout the day when they want to talk. Some people stay connected all day (or just keep the audio on and enable video when they need it).
As an alternative to Skype, you could use "vLine link": https://vline.com.
The advantage over Skype with this use case is that you don't need to add them as a contact (especially if it turns out to be someone you decide you don't want to stay in contact with).
At vLine, we provide a WebRTC-based cloud solution: https://vline.com. We're still working on some of the features you mentioned (recording), but would be happy to chat with them to see what we can do.
HD is supported, but we haven't enabled it yet for vLine link. We're waiting until we can do a better job detecting whether both ends can handle the HD stream, since the current WebRTC code doesn't do a great job of CPU load feedback (e.g., sending a 720p HD stream to a low-powered machine).
If you want to try out HD, register for a developer account at https://vline.com/developer/ and try the "Web Client". There is a drop-down menu on the "Video Call" button that lets you select HD (make sure to also choose that when you answer. The other option is to try GitTogether, which is just our Web Client with a GitHub login: https://gittogether.com.
Regarding your edit: Chrome and Firefox both support WebRTC out of the box. I'll look at the Firefox issue you mentioned (it should work).
Apple has participated in the WebRTC standard discussion (mainly pushing for H264 as the codec standard), but have kept silent on when/if they will release it in Safari.
Microsoft/Skype have been participating, but no word on when it will be in IE.
As an alternative, you could use Authy, which backs up the tokens encrypted (just don't store the Authy password in 1Password if you're worried about that being a single point of failure).