• 0 Posts
  • 70 Comments
Joined 8 months ago
cake
Cake day: June 29th, 2024

help-circle

  • Solid video, and it comes from a pretty grounded viewpoint. It’s not very techy or pros/cons-focused; it’s more about the “spirituality” of what we’re even doing with the technology in our lives. They’re obviously not a tech expert, but their mindset and “breaking point” are a lot more relatable for most casual people. This is the sort of realization that people are going to continue having as big tech encroaches further and further on their lives. E.g. their example of “it’s not one big problem, it’s many small problems that add up” with why it’s so frustrating to use Windows, but then why people continue to use it.

    It will take a “breaking point” and self-motivated change to critically evaluate the power that you’re giving to corporations and decide that you’re going to accept some discomfort in order to fix it. There will never be a perfect time to effortlessly switch your entire workflow across operating systems. I daresay that if there ever was a point at which switching to Linux was effortless, big tech would flash something new and shiny and make that no longer the case. They prey on keeping people in the path of least resistance, and understanding their strategy is the first step to doing something about it.

    Wish people would have realized this a couple decades ago, but it really does feel like Linux is re-entering public discourse as people are getting more and more jaded about their relationship with big tech companies.







  • I don’t think ‘cattle not pets’ is all that corporate, especially w/r/t death of the author. For me, it’s more about making sure that failure modes have (rehearsed) plans of action, and being cognizant of any manual/unreplicable “hand-feeding” that you’re doing. Random and unexpected hardware death should be part of your system’s lifecycle, and not something to spend time worrying about. This is also basically how ZFS was designed from a core level, with its immense distrust for hardware allowing you to connect whatever junky parts you want and letting ZFS catch drives that are lying/dying. In the original example, uptime seems to be an emphasized tenet, but I don’t think it’s the most important part.

    RE replacements on scheduled time, that might be true for RAIDZ1, but IMO a big selling point of RAIDZ2 is that you’re not in a huge rush to get resilvering done. I keep a cold drive around anyway.


  • “Cattle not pets” in this instance means you have a specific plan for the random death of a HDD (which RAIDZ2 basically already handles), and because of that you can work your HDDs until they are completely dead. If your NAS is a “pet” then your strategy is more along the lines of taking extra-good care of your system (e.g. rotating HDDs out when you think they’re getting too old, not putting too much stress on them) and praying that nothing unexpected happens. I’d argue it’s not really “okay” to have pets just because you’re in a homelab, as you don’t really have to put too much effort into changing your setup to be more cynical instead of optimistic, and it can even save you money since you don’t need to worry about keeping things fresh and new.

    “In the old way of doing things, we treat our servers like pets, for example Bob the mail server. If Bob goes down, it’s all hands on deck. The CEO can’t get his email and it’s the end of the world. In the new way, servers are numbered, like cattle in a herd. For example, www001 to www100. When one server goes down, it’s taken out back, shot, and replaced on the line.”

    ~from https://cloudscaling.com/blog/cloud-computing/the-history-of-pets-vs-cattle/



  • I think it’s hard to dig yourself out of this hole unless you’ve got early retirement on the horizon. The more you work, the less of an outside life you have, and the less you feel compelled to focus on anything but work, rinse and repeat. Your friend probably doesn’t have anything to look forward to IRL, so might as well make more money.





  • Maybe tangential but this reminded me of how much I hate setting up systemd timers/services. I refuse to accept that creating two files in two different directories and searching online for the default timer and service templates is an okay workflow over simply throwing a cron expression next to the command you want to run and being done with it. Is there really no way we can have a crontab-equivalent that virtually converts into a systemd backend when you don’t need the extra power? I feel like an old person that can’t accept change but it’s been a decade and I’m still angry.




  • I just did this, and these were my rough steps:

    1. Backup from Molly-UP
    2. Write down the code
    3. Install normal Molly from FDroid (you don’t need to remove Molly-UP yet)
    4. Open normal Molly and import the backup, log in to your account etc
    5. In your mollysocket instance, run mollysocket vapid gen and use the key as MOLLY_VAPID_PRIVKEY environment variable in docker compose, or however you’re running mollysocket.
    6. Go to notifications and change the notification type to UnifiedPush, and scan the QR code from your mollysocket instance. (I was having trouble scanning the QR code when it’s printed out via CLI, maybe because it was white on black, but the QR code from the web server page (port 8020) worked)
    7. Uninstall regular Molly-UP when you’re ready

    No real trapdoors or anything; I spent the most time trying to get the QR code to scan before finally getting it to work via the web server page.



  • I’m not sure what a good written guide for manually running linux games is off the top of my head, but generally yeah you install Lutris, install the latest Proton-GE version through e.g. ProtonUp-QT, create a game entry in Lutris with a “Prefix” location dedicated to your wine prefix, pick Proton-GE as the runner, copy the game into the generated prefix, target the normal EXE, and launch it. Sometimes if a game isn’t launching you’ll need to use “winetricks” to install vcrun2022 and dotnet48 dependencies into the wine prefix, since each Wine prefix is sort of like a copy of windows, and windows has a handful of dependencies that games sometimes rely on. I’ve heard you can also just add the game as a “non-steam game” to steam, but I’ve not bothered as Lutris gives more control. Again I can’t vouch for any specific guides, but the keywords from this post should help target a general direction to move in.