Generally GrapheneOS is looking for sufficiently secure hardware it seems.

Non-exhaustive list of requirements for future devices, which are standards met or exceeded by devices starting from Pixel 8 (shiba) through Pixel 10a (stallion):

Support for using alternate operating systems including full hardware security functionality
Complete monthly Android Security Bulletin patches without any regular delays longer than a week for device support code (firmware, drivers and HALs)
At least 5 years of updates from launch for device support code with phones (Pixels now have 7) and 7 years with tablets
Device support code updated to new monthly, quarterly and yearly releases of AOSP within several months to provide new security improvements (Pixels receive these in the month they're released)
Linux 6.1, 6.6 or 6.12 Generic Kernel Image (GKI) support
Hardware accelerated virtualization usable by GrapheneOS (ideally pKVM to match Pixels but another usable implementation may be acceptable)
Hardware memory tagging (ARM MTE or equivalent)
Hardware-based coarse grained Control Flow Integrity (CFI) for baseline coverage where type-based CFI isn't used or can't be deployed (BTI/PAC, CET IBT or equivalent)
PXN, SMEP or equivalent
PAN, SMAP or equivalent
Isolated radios (cellular, Wi-Fi, Bluetooth, NFC, etc.), GPU, SSD, media encode and decode, image processor and other components
Support for A/B updates of both the firmware and OS images with automatic rollback if the initial boot fails one or more times
Verified boot with rollback protection for firmware
Verified boot with rollback protection for the OS (Android Verified Boot)
Verified boot key fingerprint for yellow boot state displayed with a secure hash (non-truncated SHA-256 or better)
StrongBox keystore provided by secure element
Hardware key attestation support for the StrongBox keystore
Attest key support for hardware key attestation to provide pinning support
Weaver disk encryption key derivation throttling provided by secure element
Insider attack resistance for updates to the secure element (Owner user authentication required before updates are accepted)
Inline disk encryption acceleration with wrapped key support
64-bit-only device support code
Wi-Fi anonymity support including MAC address randomization, probe sequence number randomization and no other leaked identifiers
Support for disabling USB data and also USB as a whole at a hardware level in the USB controller
Reset attack mitigation for firmware-based boot modes such as fastboot mode zeroing memory left over from the OS and delaying opening up attack surface such as USB functionality until that's completed
Debugging features such as JTAG or serial debugging must be inaccessible while the device is locked

https://grapheneos.org/faq#supported-devices

I just checked my main PC which I use for playing games and development (Android and Rust), and it uses 45GB for /nix just after nh clean all which deletes all profiles but the current one. 50GB might be a bit tight during a rebuild where you inevitably have two copies of the software, but outside of that, it seems good enough.

I suppose you are aiming for impermanence? 50GB seems good enough if you're not installing too many tools. If you haven't already, take a look at nix.* options because they have some storage optimisation options. That and CLI tool called nh, which cleans stuff up for you.

{
  nix = {
    settings = {
      auto-optimise-store = true;
    };
    gc = {
      automatic = true;
      dates = "daily";
      options = "--delete-older-than 10d";
    };
    optimise = {
      automatic = true;
      dates = [ "weekly" ];
    };
  };
}

That's not AI summary, it's just an excerpt from the Wikipedia page. You can find the edit here.

https://en.wikipedia.org/w/index.php?title=2026_United_States_elections&diff=next&oldid=1383545944&diffonly=1

Does fediverse have automatic content propagation across instances? Because from what I have seen, content preservation is not the strongest suit of the fediverse unless it's a major instance, in which case we're just back to rebranded AO3.

Ah that explains it. But why would they bother with the dots? Perhaps to make it clear to others that the window is compliant? All the information I can find online seems to suggest that it's the dots that makes the window visible to the birds.

OP is def not from UK or Australia

I'd go with "literally". Its usage makes me wonder if it really is the case or it's just exaggeration. Except people are using it in series contexts.

Not even trimmiing? I also keep mine somewhat long, but I occasionally get it "tidied up".

Going through the post, I didn't expect this many people to cut their own hair.

Looks like a lot of dyeing needs to be done from what I can find. Is that the part they are having trouble with?

I suppose you miss the practicality of the military hair a bit? While I like my hair as is, I do miss how I used to be able to get out of shower within minutes and not having to dry them.

I think this has the highest number of features amongst all android keyboard apps. I really like this.