So build a wiki / forum -ish system where "accepted" papers are published. Anyone can submit a paper, or criticism, or a review, or a meta-review... With a collection of editors & "reviewers" try to keep the whole thing honest.

In other words, a wikipedia that *only* accepts original research.

But would the snake die? That question is still potentially interesting either way.

Visual Studio keeps forgetting that it is primarily a text editor. Never, ever, ever do stuff in the main thread that would stop me from entering text. I suspect this is mostly because they allow 3rd parties to run code within the editor process.

Well the Great Depression set us up for one. An angry out of work population, looking for scapegoats and easy answers.

So trying to parse the formula from the English description; [thickness] * [critical temp] = A / ([sheet resistance] ^ B), where A = [crystalline structure] * B + C

Sorry, that's got nothing to do with the point I was trying to make. Though I'm sure I rushed over a few details. I'm not talking about government debts at all. I'm talking about the total debts of the entire nation compared to GDP. The ratio of debt to GDP is higher than it has ever been. Higher than the peak in the 1930's (which was mainly because income fell). How are business and households going to pay back their debts to the banking sector? These are the debts that will not be repaid.

Paraphrasing the work of Steve Keen;

Taking out a loan to buy something, increases the income of the seller and the supply of money in circulation. A constant velocity of new loans, would result in a constant influence on economic activity. An accelerating amount of new loans will boost the economy and create jobs. The reverse is also true, decelerating loans will cause spending power to shrink and jobs will be lost. And this is borne out in economic data, there's a strong correlation between debt acceleration and change in employment.

Now, since the 60's the level of private debt has been growing, to become a significant force driving the economy. While borrowing more to buy an existing asset does nothing to create real wealth, it does push up asset prices giving us the illusion of rising prosperity. While rising interest payments are draining real wealth from borrowers.

The banking system should eventually go bust. Probably not tomorrow, but all we have managed to do so far is delay the inevitable. The loans they have issued cannot be repaid. The only question is how we are not going to repay them. Either we go bankrupt, or we find some other way to wipe off the debt.

The Great Depression started with the stock crash of 1929, lasting for the next 10-ish years. But it was the rising debts of the 1920's that were the real problem. Through the depression, those debts started to reduce. But it took the huge spending effort and industrialisation, fighting WWII to really eliminate them. Setting us up for the boom years of the 50's and 60's.

Our economic woes will not go away until we deal with the problem of our private debt. We may see another Depression, some parts of the world already are. Or we may see an extended period of stagnation. History doesn't repeat, but it sure does rhyme.

Google. Just throw the word "torrent" into your search query.

I've been using android studio for a while now, it's much better than eclipse for editing android resources or referencing them from code. But I haven't changed our build process. I still use ant & adb from the command line for building and testing everything on actual hardware.

With semantic versioning, that just means that they haven't broken backwards compatibility. Java 1.8 can still run code compiled for Java 1.0.

POODLE, BREACH, CRIME etc all require the attacker to control some bytes in the ssl stream in order to deduce other bytes that they shouldn't be able to see. POODLE requires the attacker to change the http url & form post body in order to force the alignment of bytes, BREACH and CRIME are gzip length attacks. Both require the attacker to control bytes in a http request in order to guess the contents of other bytes in the request that they wish to know, like a session cookie.

All of these are attacks on HTTP & SSL, not on SSL alone.

It's a protocol problem if a man in the middle can control some bytes in the encrypted stream. The biggest problem with attempts to keep HTTP & SSL secure, is the combination of sensitive application and user supplied data sent over the same stream in both directions.

In Australia we forced the utility companies to buy any solar power you sent to the grid using a separate meter, at a fairly high rate to encourage adoption.

Those higher tariffs are now over. So now we pay around 30-40c kWh (AUD, from memory) for mains, and they only pay about 5c kWh for any solar power you provide. But at least you're better off if you can use that power yourself.

True, but the world of programming is full of these people. If your entire team is full of them, you won't even realise it.

In Australia Telstra maintain the copper line, if there's a problem you log the fault and they fix it within 2 days or they have to pay you. Unless they file a claim for a natural disaster, which can give them an extra couple days to fix it.

At the other end of the copper, your wire may be patched directly into your ISP's equipment. Though in practice I think there are only 2 or 3 companies running the DSLAM's. Smaller ISP's then lease them per line.