89 karma · joined March 14, 2012
See also 'svn obliterate'.
The SVN UI is just horrid in other dimensions, mainly the "you can't do that at all" one.
The question is whether someone would want to subvert or rather just shut down the tor network.
The problem is more like that tor relies on a few directory authorities and the only protection they have is geographic distribution and the public outcry should a set of nation state go actually seize them.
Also, occasional upgrades.
And apparently cloudflare is much more aggressive on this front than anybody else in this business, including google - when I get a captcha it's always cloudflare (or hacker news). On those sites I can practically rely on getting one.
To turn it around, every time I see a cloudflare captcha they obviously have failed.
International companies have a way of shifting earnings into jurisdictions where they don't need to pay much taxes, since there is still a race to the bottom between countries. 'Better they pay us 2% of revenues that that other country 10%.'
(This has noting to do with the way the supply chain is done.)
But what you're describing has interesing failure modes indeed - from just successfully patching the running process to the SIVSEGV to having the target process ending up in an infinite loop (BTST).
A: Honestly, nobody knows.
You can estimate the number of leap seconds, but not know (much) in advance. Having (future) date representation chance occasionally does not lead to sanity either.
When make was written most machines would have just exploded at the sight of a typical build.xml, and downloading tens or hundreds of packages from anywhere was simply out of the question.
Also, 'dependency' means something completeley different in make as opposed to maven - I don't think modern build systems do even care much for make-style deps.
Also, I'd like to see a reference on the 'most' and 'frequently'.
Anyway, I'm only running two non-exits. :-)
(Okok, I'm not actually sure about either mac or xerox.)