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

help-circle

  • I really enjoyed the Witcher 1. What really sealed it for me was the questline

    Vizima Confidential

    The whole detective arc was very staisfying, and even if it got a little tedious, I felt like a real flatfoot running around the city chasing down leads.

    Hell, you can’t even solve the mystery by following the quest. IIRC it’s only by talking to the undertaker at the right time that you discover Raymond is a fake.


    It beat the pants off of anything from Witcher 2. I also prefer the alchemy system from TW1.

    I dislike that TW2 is basically half a game until you replay it. I’m all for branching paths, but compared to TW1 and TW3, TW2 felt way too short.




  • OneCardboardBox@lemmy.sdf.orgtoSelfhosted@lemmy.worldServer build for Family
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    1
    ·
    4 months ago

    I’d recommend BTRFS in RAID1 over hardware or mdadm raid. You get FS snapshotting as a feature, which would be nice before running a system update.

    For disk drives, I’d recommend new if you can afford them. You should look into shucking: It’s where you buy an external drive and then remove (shuck) the HDD from inside. You can get enterprise grade disks for cheaper than buying that same disk on its own. The website https://shucks.top tracks the price of various disk drives, letting you know when there are good deals.






  • Oh, judicial duels have always been bad, tending to favor the wealthy who can afford training. The pistol duel was once considered egalitarian because you were just as likely to miss your opponent regardless of how much you trained. For most of the 20th century (until the 90s) Uruguay had legalized dueling. It was mostly used by politicians and the powerful to muder journalists and lawyers who “defamed” them.

    But if we are already living in a period where the rich act with impunity anyway, I want a world where there’s a nonzero chance that we get to watch Elon Musk take an estoc to the face because of a twitter argument.






  • 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.




  • You’ve laid out one potential development cycle: FOSS from the get-go, and open collaboration welcome.

    However, that’s not the only way that a FOSS game might be developed. The code could be freely licensed, but the upstream developers refuse to accept outside patches. In that case, there’s one “original” and then if you don’t like it, build your fork.

    Alternatively, a game could be developed entirely in-house under proprietary licenses, and then only made FOSS upon commercial release. Contributor patches could improve the project, but conception of the game would be entirely the domain of its original developers.


  • 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.