Hacker Newsnew | past | comments | ask | show | jobs | submit | zeckalpha's commentslogin

levels.fyi has this

Not in my understanding. The line between neurological and psychiatric is more about history than about anatomy.

Instead, I would point to the physical trauma of a concussion as the differentiating factor.


There’s underlying physical causes for psychiatric conditions including in some cases physical trauma.

> There should be one-- and preferably only one --obvious way to do it.


It’s been pointed out to me before that:

the two ways of spacing the em dash on that quote is a joke about how it's not actually possible to do that? (And there's a third way in another line of the zen)

Do I buy it? Not sure. But apparently there’s more to this line than what it suggests.


This is not only the main reason Python turned me off, they can't even stick to it with their umpteen package managers, which is hypocrisy


I didn't see any mention of this so thought I would add:

This sounds like https://en.wikipedia.org/wiki/Retinal and https://en.wikipedia.org/wiki/Purple_Earth_hypothesis. Going through history, there have been times where the Earth has had oxygen spikes https://en.wikipedia.org/wiki/Geological_history_of_oxygen (Examples https://en.wikipedia.org/wiki/Great_Oxidation_Event or https://en.wikipedia.org/wiki/Neoproterozoic_oxygenation_eve...) Cool image showing how this process is unstable: https://en.wikipedia.org/wiki/Great_Oxidation_Event#/media/F...

You might be interested in the different photosynthesis cycles: https://en.wikipedia.org/wiki/C3_carbon_fixation https://en.wikipedia.org/wiki/C4_carbon_fixation https://en.wikipedia.org/wiki/Crassulacean_acid_metabolism https://en.wikipedia.org/wiki/Alarm_photosynthesis - this one was only discovered in 2016!

Research into these may have profound impact on climate change.


No mention of the Taj Mahal, which famously is not square so it appears square.


The Taj Mahal is 372 years old, the Parthenon 2457. And the latter isn’t even the first Doric temple.


The article mentions Erowid


N-illion = 1000^(n-1)


Isn't it more like:

  N-illion = (Size_of_Digit_Grouping)^(n-1)
Since the OP was saying groupings use to be by 6-digits, not 3-digits (i.e. "1,000") as seen today.


The original long scale makes more sense, billion, bi million, twice six digits.


Yet, mille and milli- mean thousand.


But the suffix -one in Italian is used to indicate something big - spaghetti vs spaghettoni - so a milione is a big thousand, a million.


Oracle wouldn't let you do that with Sun.

Atari has been brought back! https://atari.com

HPE is using the Cray brand: https://www.hpe.com/us/en/compute/hpc/supercomputing/cray-ex...

Coincidentally, https://www.sgi.com/ redirects to the HPE Cray link above.


the Atari brand is cute, but those products are a bit schmaltzy. we should find a way to get control of one of these brands and do an LBO of an OEM like framework or system76 for manufacturing. Apple is out of ideas and they're never going to make it in enterprise, it seems like an opportunity.


Back it up now so when the encryption is broken, it can be read!


Why does any additional encryption need to be broken? Signal dark patterns users into using insecure few digit 'pins' to protect their data, then waves some SGX hokum around that as an argument as to why very short pins have acceptable security. Of course, no one with physical access / state level resources is meaningfully impaired by SGX, so the security is just a trivial pin crackable by a speak and spell.

Concerns that were all dismissed when the insecure pin system was introduced because only contacts and settings were hosted, not content. ...

It's already known that users can't choose secure passwords even without UI that tries hard to encourage an insecure choice and that the rare ones that are secure are the ones that also get lost/forgotten. As a cryptosystem "user chooses and remembers a key" is known to be broken. So backup to the cloud really just means "hand to NSA with already known broken encryption".


If you think they've gone rogue and are working with the NSA or whatever, why can't they be doing the same thing with your e2e messages while in transit? What do they gain by getting it through backups?


> why can't they be doing the same thing with your e2e messages while in transit?

They can, and maybe they do. We can't really verify whether their servers run only what's published on GitHub (remember the MobileCoin gap? [1]).

> What do they gain by getting it through backups?

They don't need to capture the messages through backups, but the feature is a plausible reason for the users to foot the storage bills. Maybe the donations are not enough.

[1]: https://www.androidpolice.com/2021/04/06/it-looks-like-signa...



The backup is secured with "a strong key", implying that all PFS guarantees go out the window regardless of the PFS algorithm used to send the messages in the first place. Signal had great guarantees by how they both enforced a single client and was limited largely to screenshots as backups, now you'll never know if the person you're talking to has a full backup in the cloud, with metadata to match the actual conversation times, destroying the repudiability (i.e. plausible deniability) feature.


Whats to say they didn't take screenshots of the conversation that got backed up to Google Photos or iCloud anyway?

I dont think this changes anything, in regards to a malicious(/incompetent) recipient.


Screenshots can easily be forged.


Another term for theses is "raster pyramids". Here's an example from 1993: https://www.usgs.gov/publications/pyramid-system-multiscale-...


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: