Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)C
Posts
14
Comments
174
Joined
2 yr. ago

  • Are you running QEMU directly, or through libvirt (GNOME Boxes, Virt Manager)?

    EDIT: NVM I see you’ve answered that in another comment. I believe you can’t do this with QEMU directly. If you don’t need to be able to edit the VM config besides core count, disk size and RAM use GNOME Boxes. Otherwise use Virt Manager.

  • Garry from Facepunch was pretty down on Linux from Rust (the game) because of the high bug to purchase ratio and because some stuff just didn’t work on the Linux version of Unity but worked fine on Windows. I mean, fair enough.

  • I get them every now and then, but refreshing the page fixes it every time. I’m not logged in to a Google account and my browser is set to clear cookies for all but a few domains on restart, so maybe that’s contributing? Don’t restart often though.

  • Client Hello is one of the ways firewalls figure out what site you’re going to in order to block it from memory (its possible I’m getting this confused for a different request). Curious to see the impact of this.

  • Nice way to re-use an old board instead it going to landfil!

  • I can get that. I guess the concern would be that Coffee Stain start purging/deleting anything out-of-bounds? You can see the container for the plutonium waste off in the distance a little. The power plants are half in/half-out of the out-of-bounds area.

  • Oh god... I smell the desire to start using turbofuel rising...

    I'll subscribe to !satisfactorygame@lemmy.ml then!

    I don't post much on Lemmy and am trying to decide how I want to post without just encouraging everybody to go on the big instances, and so my posts don't disappear if an instance dies. Figured posting to my own instance and then cross-posting to a large instance and some smaller ones would be a good way to encourage growth everywhere but that's just me overthinking as always. Tis' an interesting experiment.

  • Just noticed the chmod command I included missed the username part. I've edited the comment to fix it.

  • I think I went Coal > Fuel + Geothermal > Nuclear. I only recently started Turbofuel just so I could finish unlocking everything in the MAM.

  • Thank you!

    I think nuclear is one of my favorite parts of the game. The process for making it and then converting the uranium waste into plutonium is massive, but feels so rewarding once it's done. Thing is, I'm only running one plant at the moment since I still have enough power production from coal and geothermal. Figured it'd be best to keep plutonium waste to a minimum until I really start needing it, unless they add a feature to bury it. I've moved my plants next to the out-of-bounds area near Niagara Falls so I can store the plutonium waste in a container out-of-bounds.

  • Thank you!

    The short but incorrect answer would be somewhere between 300-400 hours, but that's from the start of playing Satisfactory (as in, my first time playing this game) up to completing the last launch in the space elevator to get the golden mug. It also includes many nights of just leaving the game running. I originally started (with friends) in the flat grasslands and started moving a lot of production into the area you see in the video. A lot of the coal generators and things built on foundations (the stuff that looks neat) was built by friends.

  • I have started work on splitting up parts of the Sushi Train into smaller factories. The thing I liked about the Sushi Train was that if one of the assemblers/manufacturers/etc weren't producing anything anymore, then another could use the same building resource instead. That way you don't end up wasting ingot/ore production because the assemblers are idle. As an example, I have moved copper sheet, ingot and wire construction (mostly) next to the miner and each of the 3 can use 100% of the miners output. That way resources are only wasted if both constructors are idle and no ingots are needed elsewhere.

  • Fair, but I’d take a bricked PC over the data leak variety of ransomware any day. But to add to what you’re saying, I’d be more worried about a supply chain or compromised developer machine over what happened here.

  • Where is Steam writing to and where is the drive mounted to? If the drive is mounted at /mnt/games, create the folder: /mnt/game/steam, run "chmod /mnt/game/steam" and then have Steam create it's library within there. So in the end, Steam's folder will probably be at /mnt/games/steam/SteamLibrary. This way it shouldn't matter what Steam is setting the permissions to.

  • You could be the most cautious person on the planet and still end up with a virus because a game which you purchased legitimately contained a virus from a game cracking group that the devs just copy-pasted into their game.

  • This also helps mitigate the risk of people posting CSAM to attack other communities which your instance is subscribed to right? If you instance never cached the image, there's no clean-up you have to do on your end provided the original instance removes the image from their server.

    As you've mentioned, it makes sense for larger instances to have a cache, but smaller instance (especially single-user instances) may actually be better off not caching at all and just hosting their own images. As a more long-term solution which can add to this patch, it would be good if Lemmy did 2 things:

    1. Separated the image cache for images from other instances so it can be cleared automatically on a schedule. E.g. Images which are a local cache are deleted after X days. Yes there are proper caching algorithms used in filesystems which would be better long-term, but a quick solution for this is probably better than no solution.
    2. Periodically check for images which were uploaded by your own users to see if they are being referenced by any posts or comments. If not, delete them. I would imagine this could be a fairly intense operation so limiting this more fine-grained approach to images uploaded by your own users and taking the more liberal approach with cached images may help performance.