• 9 Posts
  • 50 Comments
Joined 1 year ago
cake
Cake day: June 16th, 2023

help-circle

  • For backup, maybe a blu-ray drive? I think you would want something that can withstand the salty environment, and maybe resist water. Thing is, even with BDXL discs, you only get a capacity of 100GiB each, so that’s a lot of disks.

    What about an offsite backup? Your media library could live ashore (in a server at a friend’s house). You issue commands from your boat to download media, and then sync those files to your boat when it’s done. If you really need to recover from the backup, have your friend clone a disk and mail it to you.

    Do you even need a backup? Would data redundancy be enough? Sure if your boat catches fire and sinks, your movies are gone, but that’s probably the least of your problems. If you just want to make sure that the salt and water doesn’t destroy your data, how about:

    1. A multi-disk filesystem which can tolerate at least 1 failure
    2. Regular utilities scanning for failure. BTRFS scrubs, for example.
    3. Backup fresh disks kept in a salt and water resistant container (original sealed packaging), to swap any failing disk, and replicate data from any good drives remaining.
    4. Documentation/practice to perform the aforementioned disk replacement, so you’re not googling manpages at sea.

    This would probably be cheapest and have the least complexity.



  • How about writing a script to automate the deletion, thus minimizing the chance of human error being a factor? It could include checks like “Is this a folder with .git contents? Am I being invoked from /home/username/my_dev_workspace?”

    In a real aviation design scenario, they want to minimize the bullshit tasks that take up cognitive load on a pilot so they can focus on actually flying. Your ejector seat example would probably be replaced with an automatic ejection system that’s managed by the flight computer.






  • Got a secondhand Delonghi Dedica because I had similar concerns over how much I’d use it. Previous owner installed an aftermarket steam wand, which has been a joy.

    Overall, it comes and goes in waves for me. Some weeks I pull shots every afternoon, sometimes it sits unused for a month. I enjoy taking some time to step away from the home office and prep coffee, so espresso is nice for that. I’d probably use it even more if we were more of a milk drinking household. I like my steamed milk drinks, but we don’t reliably keep milk in our fridge.

    I’m also very lazy about dialing in shots. We like to buy a variety of beans for our morning French press, so the coffee available for espresso might vary week-to-week. I’m not willing to waste coffee dialing in on a 16oz bag of beans that’ll be gone in a few days, so the quality of my espresso suffers. Do most people generally keep one kind of bean around specifically for their espresso?



  • OneCardboardBox@lemmy.sdf.orgtoArch Linux@lemmy.mlYay orphaned packages
    link
    fedilink
    English
    arrow-up
    16
    arrow-down
    1
    ·
    edit-2
    3 months ago

    In this context, orphaned doesn’t always mean you should remove it. It just means that nobody in AUR is taking responsibility to keep it updated. You still might have other packages from the AUR that depend on this one.

    Since it is unmaintained, basically anyone can now claim ownership of that package in the AUR and push updates for it. Theoretically, someone could try to distribute malware in this way.

    This is why it’s important to check the diffs of your AUR updates.






  • I know that your question is about tasting basics, and I think the answers here will get you on the right path.

    There’s a lot that goes into coffee tasting on the advanced end. Ever wonder who decides that a coffee tastes like “raspberry” and “chocolate”? A few years ago, I found a local roaster that runs barista classes, and I got tickets to their coffee tasting session. It’s really interesting to learn about all the process and procedure that goes in to tasting coffee. They take something as subjective as taste and turn it into (somewhat) objective and quantifiable data. I also learned how coffee beans are graded, and how roasters source their beans.

    The official term for this process is “cupping”, so if you’re interested, look in your area for cupping classes. I had a great time!





  • I guess it would depend on whether or not the project spawns a dedicated community that lasts for a long time. Without a wide pool of knowledgeable contributors, I think it would be hard for an original team to both support the one design while also developing the next iteration.

    Not to bring it up as a whipping boy, but let’s take the case of Wayland, which is “just” a software protocol. It was started back in 2008, and is still under active development. As more projects support it, more edge cases are coming up, which is why new features are added to the protocol all the time. In those 15 years, they’ve had to adjust to technologies that didn’t exist back in 2008, like widespread adoption of 4k HDR displays, or Vulkan. Now imagine that, but with every aspect of a computer. In 2008, DDR3 RAM was just a year old. Today we’re on DDR5 and you (probably) can’t buy a new machine that takes DDR3. PCIE 2 was the latest shit in 2007. Now I see that PCIE 7 is planned for next year.

    A global corporation can support old products while also developing new technologies because they have unfathomable labor and capital at their beck and call.

    I think that free software can keep up with proprietary offerings because the barrier to entry is relatively low. You just need free time and a source control client. I think it would be different if your project toolchain involved literal tools that cost millions of dollars.