iturnedintoanewt

Any links or hints that Google might be trying this?

That was some serious shitshow indeed. The director completely focused on the first episode and a very few parts on the other ones. When they were rushed, they sub-hired some Korean studios, and in the end even cheaper Chinese ones, if I recall correctly. I think the result speaks for itself. An absolute disaster.

They have no work left to be done.

Yeah that's when i started paying attention to what this guy does... Really good series.

I...disagree. I think Mike Flanagan's previous work in both making new IP horror movies and shows, and making remakes/follow-ups while honoring the original material (ie, Doctor Sleep) has been rather consistently decent. If it's horror related, I pay attention about what this guy might do next. And some others, like Ari Aster, but to me Flanagan is actually a good sign.

Man...I really wanna like postmarketOS. But to be honest I'm not sure there's any recent device (or maybe not that recent?) that has full hardware supported. Like, something you could daily drive, while not having any issues with any of the hardware parts.

I mean, if you get a way to invoke X/wayland to render in a decent way instead of the VNC callback methods currently being used, I might really want to think about this. But otherwise I don't think we'll be getting an alternative UI anytime soon. Also I very much doubt this is in Google's interest to allow people to run a different graphical interface.

Yes, I understand all this but....If I got the wrong password, I should, A) get some feedback that I have clicked Enter and attempted a login, and B) get feedback that my attempt failed, right? All I get is a frozen screen unresponsive to any input at all.

Nope. Full on original surface keyboard. Works on BIOS, works on Grub...and then on that specific step, no input is reflected on the screen. No keys being typed, no failed login message being shown, nothing reacts.

...I think you have something here. If I create a random password and save it via nano on a brand new file, and use this file as passphrase during the initial creation...it then doesn't let me open the encrypted device. It says no key available with this passphrase. When you input the cryptsetup open, you're only allowed to manually type the passphrase (it no longer accepts a file with the passphrase, I think). Curiously, both the file and the passphrase I type manually...are pasted from the clipboard from the same password randomly generated on bitwarden and then copied to the clipboard. And yet, it seems something doesn't match.

EDIT: Seems when you 'open' with a file, the appropiate way is cryptsetup luksOpen /dev/sda encrypted --key-file /home/user/encryptedSD.txt

You have to add the file as a key file. Just adding the password to the file isn’t enough.

cryptsetup luksAddKey /home/user/EncryptedSD.txt /dev/sda

Thanks! I think you're onto something here. SOrry what's the purpose of adding the key? Does it get stored in cryptsetup's internal storage so you never have to input it again?

Nowhere in this article: the plane's autonomy. Its main catch, and the main unsolved problem to make electric flying a thing.