I'd like to give jj another go but I found the "all files must be tracked/committed" approach to really break my workflow.
I have a lot of temporary uncommitted files, which are not ignored or excluded. Some may eventually be committed but most won't.
Being then forced to commit these (but only some due to file size) just gets in the way and impedes things like cross branch debugging
A checkout is a working space after all, why can't it be (temporarily) dirty whilst you work?
Been using/abusing wezterm for years, my scrollback is set to 1000000 and text selection has never been a problem... copy mode however does make it even easier
For the oauth login it requires the following permissions:
View basic information about your account, Manage your data in Google Reader, View your email address
Manage your contacts, View and manage your Google Contacts, Perform these operations when I'm not using the application
Why would it want access to view AND MANAGE my contacts? This seems a bit odd.
Memcache is designed to be run on a trusted network and only accessed by trusted clients. Therefore sharing a memcache daemon in its current state is not recommended at all.
Many sites also use memcache to cache page fragments that will be sent verbatim to clients with the rest of the webpage.
As Marco demonstrated in his slides one can easily inject into caches and if one can change the values of keys related to page fragments then it is a major security risk.
Since the Guidelines/FAQ has nothing on this specifically and it might be useful to one(Maybe more) HN readers I believe you should post a "We are hiring" thread.
Especially if no one gives any good reasons why not to in this thread.
I might be missing something here, but isn't David Ulevitch
affiliated with OpenDNS which should be more than capable of running everydns? Its maybe not their primary function, but its pretty close.