815 karma · joined April 21, 2020
Sending things unencrypted that users have every reason to think are encrypted is extremely irresponsible. And I assumed, as I think is perfectly reasonable, that everything in an E2EE room is in fact end-to-end encrypted. I'm very disappointed to find out this way that it's not (and won't be for the foreseeable future), and I don't see any justification for failing to making users aware of that.
All that said, I love Matrix, will continue to use it every day, and am hugely rooting for the success of the project. Thanks for all your hard work on it!
It's more like, "Welcome to our federated decentralized service. You can log in with your Facebook account if you want to." Which doesn't sound like a bad thing to me.
More choices for users is usually a good thing. If users' choices have bad consequences, that's not Matrix's fault. Though maybe Matrix should warn people that if 3rd-party cuts them off they'll be locked out of their Facebook account too—choices need to be informed!
Source: http://www.uigi.com/h2_conv.html
Source: https://en.m.wikipedia.org/wiki/Starlink -- in the table of launches there's a column for orbit height.
> I spent many hours with Cade, taking his calls and emails morning or night, at the playground with my kids or wherever else I was, answering his questions, giving context for his other interviews, suggesting people in the rationalist community for him to talk to…
and
> Was there some better, savvier way for me to help out? For each of the 14 points listed above, were I ever tempted to bang my head and say, “dammit, I wish I’d told Cade X, so his story could’ve reflected that perspective”—well, the truth of the matter is that I did tell him X! It’s just that I don’t get to decide which X’s make the final cut, or which ideological filter they’re passed through first.
> I don’t want to accuse the New York Times of lying about me, exactly, but if they were truthful, it was in the same way as that famous movie review which describes the Wizard of Oz as: “Transported to a surreal landscape, a young girl kills the first person she meets and then teams up with three strangers to kill again.”
I have only gained respect for Scott, and lost respect for the NYT, throughout this while saga. Hopefully this is the end of it.
Edit: in the spirit of moving on, here are two of my favorite articles since his return, one enlightening, one funny:
"WebMD, And The Tragedy Of Legible Expertise" -- https://astralcodexten.substack.com/p/webmd-and-the-tragedy-...
"List of Fictional Cryptocurrencies Banned By The SEC" -- https://astralcodexten.substack.com/p/list-of-fictional-cryp...
I could be wrong here, what do I know. But that's my read on the situation, and it's why this sort of thing doesn't bother me that much.
Anyway, landing Starship involves a bunch of things never before attempted: landing a fully-reusable second stage, landing a vehicle of this size, relighting and running engines during the belly-flop-and-flip maneuver, and flying and relighting full-flow staged-combustion engines. Probably some other firsts too.
Actually, I guess if DwarFS is a kernel module and decompresses blocks before they hit the kernel's filesystem cache, then the kernel cache would do it? I'm not sure how to tell from the README if DwarFS is a kernel module or not. So I guess I'm just confused and looking to learn -- what kind of kernel caching did you have in mind?
Well, sort of. The first assignment was to write a bootloader in x86 assembly. For the second assignment we were given a bootloader and a partially-implemented kernel, and we had to finish the kernel by writing a non-preemptive (cooperative) scheduler (including implementing context switching and so on). Third assignment same thing but a preemptive scheduler. And so on. The partially-implemented kernel is very rudimentary—kernel threads but no userspace threads or forking, no filesystem, no virtual memory and no actual difference between kernel mode and user mode (until the virtual memory assignment, in which the partial kernel we were given did actually do ring transitions), etc.
Anyway all this is to say that we were running a very very bare-bones, stripped-down kernel, and even then it was annoyingly slow, so I expect that it would be still be extremely slow running a "real" OS. It's my understanding that that's not really what Bochs is for, though. If you want to run Win95 use a normal VM; Bochs is meant to be a low-level x86 development tool. Though again that's just my impression, so I could be wiong in that.