HN user
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).
CLion also has clang-tidy built in: https://blog.jetbrains.com/clion/2017/04/clion-2017-2-eap-cl...
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).
Looks like it:
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.
https://blog.jetbrains.com/clion/2017/01/clion-starts-2017-1...
You might find this interesting: https://www.1843magazine.com/features/the-scientists-who-mak...
A more detailed article: https://www.1843magazine.com/features/the-scientists-who-mak...
You actually don't need a separate editor for most of the languages (minus C++ with CLion). It's not entirely obvious, but if you use IntelliJ IDEA, there are plugins for the other languages that provide the equivalent functionality of PyCharm, Ruby Mine, etc: https://plugins.jetbrains.com/idea/plugin/631-python https://plugins.jetbrains.com/idea/plugin/1293-ruby https://plugins.jetbrains.com/idea/plugin/6610-php
+1. Gerrit has a similar way to express access permissions that differentiate between a "contributor" and a "developer": https://gerrit-review.googlesource.com/Documentation/access-...
The latest version of Google Photos (2.0) builds in the Motion Stills functionality:
https://itunes.apple.com/us/app/google-photos-free-photo-vid...
Beyond Compare is the best I've found (especially for complex merges): http://www.scootersoftware.com/
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/.
If you ever want to integrate real-time video chat as well, send us a note at vLine: https://vline.com. We actually have what we call a "GitHub identity provider" (https://vline.com/developer/docs/getting_started) that should make it really easy.
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).
Disclaimer: I work for vLine.
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.
Sorry you had a bad experience. It does work in Firefox, although there are bugs in the current stable version (which is why we are encouraging Chrome). Specifically, two nasty ones are audio echo (https://bugzilla.mozilla.org/show_bug.cgi?id=916331) and audio latency (up to 10 seconds: https://bugzilla.mozilla.org/show_bug.cgi?id=785584).
What version of Firefox are you using? What OS?
Yes, it supports multiple people -- we probably should have mentioned that.
We're going to be covering a WebRTC codelab (written by Sam Dutton at Google) at the SF HTML5 WebRTC Hack Day (http://www.meetup.com/sfhtml5/events/139666482/) tomorrow:
https://bitbucket.org/webrtc/codelab
Another good set of WebRTC resources: https://github.com/muaz-khan/WebRTC-Experiment
For STUN/TURN, you'll probably want to take a look at this server: https://code.google.com/p/rfc5766-turn-server/
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.
Glad you like it!
We're always excited to see the new things that people build with our platform. The goal for our developer platform is to enable massive parallel experimentation with WebRTC so that people can create applications that are completely new and different from anything that exists today. We believe that by abstracting out the global server backend (and browser differences, etc.) from WebRTC there is a much larger market of developers that can build amazing things involving communication than ever before while only using JavaScript.
If you need any help along the way, don't be shy to contact us (@vlineinc, support@vline.com, http://stackoverflow.com/questions/tagged/vline)
Looks like GitHub is back up!
GitHub is currently down so logging in doesn't work: https://status.github.com/