Nope, based on the same article a few lines lower:
> The burden of dementia is increasing exponentially especially in Asia-Pacific region, where more than 60% of the population reside [34]. The prevalence of dementia seems to be higher in developed countries, like Japan and Korea, than in countries with low incomes in Asia. A Japanese study found that the prevalence of dementia equals 11% among those aged more than 65 years [35, 36], whereas a Korean one found the prevalence of 6.3% [17]. Another study conducted in Korea, the Seoul study, showed that the prevalence of dementia, excluding very mild cases, was about 5.3% for overall dementia and 4.3% for AD [37].
> The prevalence of dementia greatly varies between different ethnic groups living in the same country, like in Singapore, that is probably the most multicultural region of Asia. A Singaporean study showed low standardized dementia prevalence among the ethnic Chinese (2.5% among the elderly) when compared to the ethnic Malays (4.0% among the elderly) and this finding was independent of the frequency of vascular risk factors [18]. Whereas these differences are due to different genetics or lifestyle it remains a matter of debate.
As somebody who has also lost a chunk of my finger to a mandolin (regrew including print) this thread has convinced me that mandolins are just not worth it.
There are a lot of places that we were seeing users drop off the radar when trying to install. Through a combination of logging analytics and user studies we figured out what the main problems were and designed this flow to solve them.
(See my post from last week for more context on why we built this: https://news.ycombinator.com/item?id=8168792)
>>
Instead, we created a custom version of the signing tools which complied with the Authenticode spec (for Windows) while letting us safely modify content for each binary. Our custom tool allows us to create an unverified section of the binary in a way that is compliant with the Authenticode spec.
>>
Can you offer some more info on this topic in a follow-up post?
Inside the Authenticode signature, there is an area for unauthenticated attributes (e.g., if you timestamped your executable, the timestamp (PKCS#9) is stored as an unauthenticated attribute,
http://blogs.technet.com/b/srd/archive/2013/12/10/ms13-098-u...). These attributes are not verified by Windows Authenticode when the executable is run. So if you can add a new unauthenticated attribute into the signature, you can make any change we want to that attribute without invalidate the signature.
In order to inject an unauthenticated attribute to the signature, you may want to use osslsigncode for signing (instead of MS signtool).