• 0 Posts
  • 22 Comments
Joined 6 months ago
cake
Cake day: April 7th, 2026

help-circle

  • mlfh@lm.mlfh.orgtoLinux Phones@lemmy.ml•Pixel 3a
    link
    fedilink
    English
    arrow-up
    5
    ·
    13 days ago

    I run postmarketos on my old pixel 3a, and it works great as a linux device, but I haven’t used it for calls/sms. The wiki says sms should work but calls are only partially supported.

    If yours is just sitting unused, postmarketos is definitely worth a try.

    edit: apparently postmarketos changed its name to nura three days ago, and that link redirects to their rebranded wiki







  • mlfh@lm.mlfh.orgtoAsklemmy@lemmy.ml•Would you call yourself a feminist?
    link
    fedilink
    English
    arrow-up
    20
    arrow-down
    2
    ·
    27 days ago

    I’m sorry, but that is a huge crock of horseshit with absolutely nothing to back it up but vibes. That’s like saying the abolitionist movement achieved nothing because it is superceded by a broader class struggle against capitalism.

    Women fought for and won the the right to self determination, the right to vote, the right to divorce, the right to bodily autonomy, the right to be legally treated as persons instead of as the property of their husbands, etc, and none of that is diminished by its byproduct of a larger workforce being better for capitalists. “Women haven’t won anything” fuck outta here


  • mlfh@lm.mlfh.orgtoAsklemmy@lemmy.ml•Would you call yourself a feminist?
    link
    fedilink
    English
    arrow-up
    46
    arrow-down
    2
    ·
    27 days ago

    I was raised with Gloria Steinem’s definition of feminism shaping my understanding, and have called myself a feminist since I was a child:

    “A feminist is anyone who recognizes the equality and full humanity of women and men.”

    A more modern and inclusive version of that same idea, adopted by UN Women:

    “Feminism is the belief that everyone, regardless of gender, should have equal rights and opportunities.”

    Feminism is a very complex grouping of movements and ideologies, but I think “membership” within them is very simple: if you believe in equality regardless of gender, you’re a feminist.


  • I use windows 11 for work as a linux/hpc admin, as it’s a mostly microsoft shop. Most of my work is done in a wsl almalinux terminal, which works fine.

    The most important things I’ve done to make the rest of it more comfortable all come from the powertoys suite:

    • fancyzones, to replicate a tiling window manager (I really hate floating windows)
    • workspaces, to group apps and window placements so I can easily launch mail/chat/terminal/browser into predetermined places, etc
    • keyboard manager, to set up shortcuts to everything
    • run, for a keyboard-driven launcher

    With all of that, if you squint and don’t think about it too much, it’s almost like a dreadfully slow sway desktop haha







  • I run the immich container stack on a vm with 4GiB memory and 2 cores, with db on local disk and external libraries over smb, and it runs perfectly fine. I offload the machine learning jobs to another sometimes-on machine, sometimes, but don’t really need to unless I’m dumping thousands of new images into the external library at a time and want it all to process quickly.


  • Looks like both of your vms probably have the same mac address - the 172 ip address is likely a self-assigned fallback when the dhcp server replies to the second vm that it can’t give it an address. Double-check and make sure the mac address in each vm’s proxmox network adapter settings match your pfsense dhcp reservations, and let me know if that resolves it.




  • From the grapheneos faq section on device support, which details the kinds of hardware and firmware security features required and present on pixels (but may be missing on other devices):

    Hardware, firmware and software specific to devices like drivers play a huge role in the overall security of a device. The goal of the project is not to slightly improve some aspects of insecure devices and supporting a broad set of devices would be directly counter to the values of the project. A lot of the low-level work also ends up being fairly tied to the hardware.
    Non-exhaustive list of requirements for future devices, which are standards met or exceeded by current Pixel devices:

    • 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