[–] 3 points 13 hours ago (3 children)

Another for KeePass + Syncthing.

No self-hosting required. Just install both on whatever devices you need to access passwords, and let Syncthing handle the rest. KeePass is designed to handle multiple simultaneous connections to the database and can sync on the fly.

  • source
  • [–] 3 points 14 hours ago

    Memorizing passwords and keeping them in your brain

    Not feasible. This is why password managers exist.

    A notebook written in cryptic script and kept in a safe behind a ravenous tiger

    Sarcasm detected, but no.

    Swearing off technology and living in secret in a cave

    I mean....

  • source
  • parent
  • context
  • [–] 4 points 14 hours ago* (1 child)

    Not slop. Just because someone decided to generate a readme or accept generated code doesn't mean its slop.

    The Fossify dev has been pretty clear that they review all the code that comes through before shipping it.

    Hell, did you even read the link you posted?

    • AI-assisted pull requests are permitted, provided they follow the contribution guidelines.
  • source
  • parent
  • context
  • [–] -1 points 14 hours ago*

    "Wow, this SOC that was never made to compete directly with other flagship-tier SOCs is getting destroyed by flagship-tier SOCs"

    Who'd have thought.... Don't get me wrong, I have my own reservations about the Tensor SOC, but anyone who knows anything about google should already know that the Tensor was optimized for machine learning and other shit over raw performance.

  • source
  • [–] 4 points 1 day ago* (1 child)

    Graphene only supports devices that have the hardware necessary to utilize the security features Graphene devs implement. Right now, the Pixel phones are the only devices with said hardware that also allow third party signing keys to lock the bootloader.

  • source
  • parent
  • context
  • [–] 6 points 2 days ago* (1 child)

    This isn't a comparison between Proton and Google. This is a criticism of how Proton is becoming just like Google. A lot of us moved to Proton specifically to get away from Google, and now here we are, having to move yet again because the CEO turned out to be just like every other big tech CEO. The most damning part is that the Proton Foundation board has said nothing.

  • source
  • parent
  • context
  •  

    Finally....FINALLY had time to start moving everything over from my old Mac Mini-based NAS to my "new" NAS.

    For reference: https://lemmy.dbzer0.com/post/61180593

    So far so good! Ultimately, I decided to start with a fresh install of the most recent OMV release (v8.5), and migrated my existing mdadm-managed RAID5 array to that. OMV picked it up immediately, which made that part very easy.

    The tricky part I'm dealing with now is remapping the various shares to my Proxmox cluster and VMs. Because I started fresh, I changed things up a little bit and created a second "disk" for each of my four Proxmox-hosted Docker VMs, which will hold those containers' user data (not the container itself). The secondary VM disks are hosted inside Proxmox's own NFS mount from the NAS.

    Maybe there's a better way to map the storage, but honestly I've learned an absolute shitton about how to properly set up Linux permissions and service users through this whole process. Plus, if the Mac mini was shut off from a power interruption or whatever, I would still have to manually power-on each disk in its USB-connected enclosure.

    Unfortunately, during this migration process, one of my 4TB Reds refused to play nice, and checking the SMART stats showed multiple failing sectors. It has 69k (nice) hours, same as its twin. I had anticipated this, as I bought the first pair of EFRX Reds back in 2018, so about a year or two ago I added a newish 4TB Black as a hot spare (already had it, wasn't using it for anything else). By the time I found the dying Red, mdadm had already automatically removed the Red from the array, pulled in the spare Black, and rebuilt the array. Fucking awesome. Both legitimately and sarcastically...

    The neat part is that the case is 100% ATX compliant. Everything works with the new mobo, from the power button, to the lights, and even the front USB ports.

    Obligatory pics!

    Fully assembled:

    OS install:

    And its original config from HP, right before I tore it apart. Check out that dust blanket:

    Full specs:

    Part Name
    Case HP ProLiant ML110 Gen 2 (2004-ish)
    Motherboard Asus PRIME Q270M-C mATX
    CPU Intel Pentium G4560T
    Memory Samsung 1x8GB DDR4-2400
    Power Supply Rosewill Capstone 650W
    CPU Cooler Thermalright Assassin X SE
    Case Fan Noctua A12x25 120mm
    Operating System OpenMediaVault v8.5
    OS Drive Toshiba 128GB M.2 NVME SSD
    Storage Management LSI HBA 9211-8i - IT Mode
    Storage Management Rosewill 4 x 3.5" HDD Hot-Swap Cage (+fan)
    RAID5 Storage WD Red CMR 4TB 3.5" HDD
    RAID5 Storage WD Red CMR 4TB 3.5" HDD
    RAID5 Storage WD Red CMR 4TB 3.5" HDD
    RAID5 Storage WD Black 4TB 3.5" HDD (Hot spare - it's CMR, too!)
    RAID5 1:1 Backup WD Red Plus CMR 8TB 3.5" HDD
    Camera Storage WD Purple 1TB 3.5" HDD
     

    Without getting into too many revealing details, my wife and I have a handful of Ring cameras that we are looking to replace, especially with the bullshit they've been trying to pull lately. They are used often, indoor and outdoor.

    Last year, I tried rolling my own replacement with a standalone Frigate machine and the HA integration, but that ended up falling flat on it's face. I am not looking to troubleshoot that setup - that ship has sailed. Moving on.

    Enter Unifi Protect. I'm already familiar with Unifi, my network has been running fantastically on the OG trash can UDM since it came out, plus a U7 Lite AP for extra coverage in our tall-ish 3-story duplex. The place is wired with Cat5, but since we rent, some areas will have to be handled with wifi-only units - the G4 instant looks suitable for this.

    Questions:

    1. Ring has a very "wife-friendly" interface. How does the Unifi Protect UI fare in comparison?
    2. I'm looking at the NVR Instant to handle about 6x FHD cameras. Would a 1TB WD Purple be suitable for that?
    3. Motion detection - How is Unifi Protect with this compared to Ring? Better, worse, or equivalent? How flexible is it?
    4. (less important) I'm reasonably certain I can set up a doorbell replacement via HA, zigbee button, and a G4 Instant. No Cat5 to the front door unfortunately, just the usual pair of wires to the wall-mounted ringer inside. POE is not an option here. Viable? Or should I do something else?
     

    Edit 10/8/26 - finally migrated: https://lemmy.dbzer0.com/post/76651987


    I'm finally getting around to migrating my OMV-based NAS from its current "2014 Mac Mini + USB multi-drive enclosure" setup to a more reliable build that doesn't rely on USB. But I'm torn on CPU choice.

    The "new" system is based on Intel 7th gen hardware, since that's what the majority of my whole homelab runs (with zero complaints). The motherboard is an Asus Prime Q270M-C, meant for more commercial applications, and supports Intel's vPro/AMT/ME/whatever it's called ("vPro" from here onward) OOB management setup. I would really like to utilize vPro since I'm familiar with it and most of my machines have this enabled (and not accessible from outside my LAN).

    The only compatible 7th gen CPUs with vPro are the i5-7500/T, i5-7600/T, and i7-7700/T. All are cheap (≤$50), easy to find on eBay, and I have no issues using the 35W T SKU. That said - I have a spare, yet perfectly functional Pentium G4560T sitting on my desk, but the only reason I haven't installed it yet is because it doesn't support vPro. I also have a 6th gen i5 (which the Asus mobo also supports) in an unused Optiplex 3040 SFF somewhere in my basement, but I don't think that CPU supports vPro. I should check...

    Anyway, I have some options:

    1. Use the G4560T and deal with no vPro.
    2. Swap the G4560T for the i7-7700T currently installed in my HA instance (Lenovo M710q), but then deal with virtually zero CPU overhead in HA.
    3. Buy an i5-7500/7500T
    4. Buy an i5-7600/7600T
    5. Buy an i7-7700/7700T

    I don't have an issue with any of these options, even losing vPro is something I can deal with. But I like having overhead, and hate having extra hardware laying around.

    What say the Lemmings?


    P.S.: For those interested, this is the planned NAS build.

     

    ....then proceeded to get stoned and watch it roam the house, doing it's thing.

    And then it dawned on me - I now have a completely self-contained autonomous robot that is free to roam my house, not attached to any cloud services, doing actually productive things; and I have full control over it.

    I know it's an odd thing for a grown-ass man to get excited over, but I can attest to the fact that 14 year-old me would be over the fucking moon about this. My parents got me the first Lego Mindstorms set for Christmas when I was younger, and I had an old Palm V handheld from my uncle; I managed to figure out how to control the Mindstorms controller with the Palm V's built-in IR blaster, using just a "universal remote" app.

    How far we've come.... Just accomplishing this has given me a renowned motivation for self-hosting shit; it's incredibly freeing. And knowing that the manufacturer of this vacuum could access it at any point and just outright shut it off without my knowledge.... I don't have to deal with that anymore.

    The robot is a Wyze "Robot Vacuum" (model WVCR200S), which is based on the 3irobotix CRL-200S - the very same robot one author recently discovered was being intentionally shut off after he had blocked some telemetry URLs. I bought it for $20 on eBay. Fully functional, but the battery only lasted ~10 minutes from a full charge. Luckily it just uses four 18650 cells in series, so replacing those was a pretty simple task. I did not buy a whole new pack (most of them are expensive and falsify their true capacities), rather opting for individual Molicel P30B 3000mAh cells for ~$5 each. I ended up having to peel off the nickel tabs from the old cells and carefully solder them to the new cells, as I don't have a spot welder. Lots of flux and a soldering iron set to 450C were key here. I would not recommend that method 😅.

    Edit: My parents dropped by last night and I gushed about it to them... My dad is a tech guy, so he was pretty interested. My mom was more "I have no idea what you're talking about but I'm happy that you're happy" 😂😂

    view more: next ›