A working nuclear thermal propulsion (NTP) engine was already built in the 60s under NASA’s NERVA project. It is one of the highest technological readiness level solutions we have to the dilemma of high specific impulse versus high thrust present in the current spsce engine technologies. Imo we need something like this to make manned interplanetary missions viable.

Fair, although you’re probably fine for “hosting jellyfin for your family” levels even then. If cloudflare boots you, swap to a free tier Oracle Cloud VPS and set up an nginx proxy.

They removed that clause. Ctrl-f “video” on their ToS page gives 0 results

https://www.cloudflare.com/en-gb/website-terms/

Example: https://grapheneos.org/faq#baseband-isolation

Yes, the baseband is isolated on all of the officially supported devices. Memory access is partitioned by the IOMMU and limited to internal memory and memory shared by the driver implementations…Earlier generation devices we used to support prior to Pixels had Wi-Fi + Bluetooth implemented on a separate SoC. This was not properly contained by the stock OS and we put substantial work into addressing that problem.

Baseband modems were not isolated from kernel memory in stock Android, GrapheneOS had to do it themselves using the IOMMU. We do not know for sure due to the proprietary/closed-source nature of baseband modem drivers, but we have no reason to assume any OEM (Samsung, Xiaomi etc) implemented proper isolation of baseband modem and system memory.

AI models are universal approximators f such that y=f(x,w) with optimizable weights w that minimize some metric L(y). You can come up with a hand tuned approximator yourself that matches/beats an AI model. Does not change the fact that any approximator attempts to guess (i.e. “hallucinate”) the output y based on the prior x.

Hallucinated frames like DLSS3. Completely unnecessary, just like the hallucinated pixels of DLSS2/FSR2. Dialling a couple of settings down to medium looks much better.

Think it’s not supported for the root filesystem anymore but that’s not my usecase anyway. Still supported for non root filesystems.

ZFS without having to faff around with DKMS

deleted by creator

GrapheneOS has strict sandboxing for all apps. App A cannot talk to App B unless given explicit user permission. Google Play services is not installed by default, and if you do install it, it’s subject to the same sandbox. This basically addresses all userspace tracking concerns, unless you actively choose to weaken those defaults.

GrapheneOS has strict sandboxing for all apps. App A cannot talk to App B unless given explicit user permission. Google Play services is not installed by default, and if you do install it, it’s subject to the same sandbox. This basically addresses rid of all userspace tracking concerns, unless you actively choose to weaken those defaults.

(There are still concerns associated with the closed source firmware of the baseband modem)