• 0 posts
  • 65 comments
Joined 3 years ago
Cake day: June 23rd, 2023
  • Not really. It was initially called the Quinnspiracy, after Zoe Quinn, author of Depression Quest, an e-choose-your-own-adventure-book that got some coverage in videogame journals.

    Shit blew up when her ex made massive accusations about sleeping with the journalists in question. Then some actor coined the term Gamergate, and their targets expanded to then-journalist Anita Sarkeesian (I think she works more as a DEI advisor now) and indie game developer Brianna Wu.

    Make no mistake, the games journalism industry was not spotless, far from it. But the rampant misogyny in Gamergate cannot be ignored.

  • I call them id-style shooters myself, but there is a bit of word play I like in the term ‘boomer shooter’. On top of referencing the age of the audience when they first arrived (albeit incorrectly), it is also a reference to the fact that the optimal strategy for these games is simply to blow things the fuck up. There is very little tactical play beyond what weapons to use for a given situation, and these games really love their explosive barrels and rocket launchers.

  • Just reading through the rust book (a week, maybe? I don’t remember how much time it took) will make you able to confidently write a simple CLI program.

    You can do the same in Java or especially Python from zero much, much quicker.

    Also you can learn to go beyond simple CLI programs in those languages much quicker, because you don’t have to worry about memory management.

  • The most manual way is what C does, which is requiring the programmer to check memory safety by themselves.😛

    The difference is, Rust will throw a tantrum if you do things in an unsafe way. C/C++ won’t even check. It’ll just chug along.

    Rust is really not that harder than Java or Python.

    As someone who’s done all three, the fuck it isn’t.

    If you are familiar with C/C++ best practices to any operational level, those things will translate over to Rust quite nicely. If not, that learning curve is going to be fucking ridiculous with all the new concepts you have to juggle that you just don’t with either Java or Python.

  • It’s very, very useful.

    For one thing, its a ridiculously easy way to get cross-distro support working for whatever it is you’re doing, no matter the distro-specific dependency hell you have to crawl through in order to get it set up.

    For another, rather related reason, it’s an easy way to build for specific distros and distro versions, especially in an automated fashion. Don’t have to fuck around with dual booting or VMs, just use a Docker command to fire up the needed image and do what you gotta do.

    Cleanup is also ridiculously easy too. Complete uninstallation of a service running in Docker simply involves removal of the image and any containers attached to it.

    A couple of security rules you should bear in mind:

    1. expose only what you need to. If what you’re doing doesn’t need a network port, don’t provide one. The same is true for files on your host OS, RAM, CPU allocation, etc.
    2. never use privileged mode. Ever. If you need privileged mode, you are doing something wrong. Privileged mode exposes everything and leaves your machine ripe for being compromised, as root if you are using Docker.
    3. consider podman over docker. The former does not run as root.
  • Google drive isn’t self-hosted though,

    Doesn’t matter to most people, and for those it does matter to, there’s OwnCloud and a ton of other options

    and they charge for any significant amount of storage.

    Storage costs money, dude, and GDrive don’t cost much.

    I’m running Ubuntu server, so there is no desktop to access via rdp, and I don’t have to open an ssh port to access this.

    If you are worried about opening SSH to the internet, you should be absolutely fucking terrified of opening a browser based admin portal to the net. SSH is fucking bulletproof compared to any web admin console you can think of.