One wonders if Microsoft/npm.js should allow new packages to be published immediately following an account email address change? I mean changes to email address are already recognized as potential attack vectors, so emails are sent to the old address warning of potential account take over. But this seems to have been done at night, so the warning email would not be seen yet. Even so a new package could be published and served to the world immediately. Unless I misunderstand something about the facts this would indicate an extreme lack of imagination in the people at Microsoft who already went through several cycles of hardening the service against supply chain poisoning attacks.
Inflation is about what goes on inside the country. So you can have inflation internally while the domestic currency strengthens against foreign currencies, and vice versa.
If your currency is falling against foreign currencies but prices are also dropping domestically, you get deflation. This was happening in China a couple of years ago, and they were exporting this deflation to other countries.
I think you have it backwards. The brain doesn't "know" what's supposed to be sensitive or pleasurable. It boots up with no training data after all. It machine learns what's sensitive due to a combination of nerve density and other factors. We haven't figured out all the other factors yet. But that's why there's a correlation between nerve density and sensitivity: density means sensitivity.
reply