As someone who has a person with psychosis in my family, I don't think you can find any interesting insights from the details of their delusions. It's like dissecting dreams or AI slop, there is no hidden meaning behind it. Usually best not to discuss it.
I doubt that it does any advanced HDR stuff like modern phones do so it's going to clip unless exposure is controlled. It's a shame that in this day and age camera companies can't achieve as great instant results as modern phones even though they have much larger sensors and better optics.
I don't think anybody in my non-tech circle even knows that messages are encrypted. It's just a convenient way to message people and share pictures from android phones. At some point in the past it was viber and before that fb messenger. I know older people who wouldn't know how to attach a document to an email but can share vacation photos via whatsapp, and we have group chats between friends and family. People also care about their chat history, and if they don't know that the data is encrypted and needs to be backed up, they loose it when transferring to a new device. It's happening all the time, a lot of common users would expect chats to just stay in the cloud somewhere and be available.
Windows is only getting worse because of all the bloat like ads, telemetry, react ui, frequent updates (needs to restart like every other day), recall and so on. Software from 20 years ago feels snappier, even though they didn't add anything new.
There is a great netflix documentary made in 2018 called "the long road to war". By the time the shooting happened a lot of other pieces had fallen into place. Basically, there were people in military circles and in the government that dictated the geoplitics game based on which country has leverage, who has the train tracks or a port to handle the logistics of war, and there was a certain zeitgeist, an egregore if you will, and things were ripe for conflict.
> Or for whatever reason it can't even get the time right. Every single time I boot into it, my clock time is wrong.
Dual booting will do that because linux & windows treat the system clock differently. From what I recall one of them will set it directly to the local time and the other always sets it to UTC and then applies the offset.
The most reliable fix is to get Windows to use UTC for the hardware clock, which is usually the default on Linux. (It's more reliable because it means the hardware clock doesn't need to be adjusted when DST begins or ends, so there's no need for the OSs to cooperate on that.)
That flag has been broken for at least several Windows versions, unfortunately. A shame, given that that's the only sane way of using the RTC in the presence of DST or time zone shifts...
That's exactly the type of Windows-ism I'm talking about. Two options (use UTC or the local time), and Windows chose to pick the nonsensical one.
Yeah, well, I use ntfs in Linux. It somehow knows how to treat the partitions. Even though it can't fix the issues when they arise (which almost never happens) — there's no chkdsk for Linux. So, I just don't understand why Windows can't automatically sync the clock (as it explicitly set to do it) when it boots? Why does one have to get creative to fix the darn clock? If I can't even trust the OS to manage the time correctly, what can I trust it with, if anything at all?
reply