• 0 Posts
  • 154 Comments
Joined 1 年前
cake
Cake day: 2025年2月7日

help-circle



  • You’re perfectly right, of course, but I’d be wary of projecting the assholery of the elites onto the bulk of the people actually fighting that war, and particularly on the peasants that bore the cost of plundering armies taking their supplies and occasionally daughters or wives.

    Either way, the topic of defending againt malware or AI is closer to the type of small-scale raiding warfare that passes beneath the notice of the recording elite (or predated record-keeping entirely). Accordingly, these will not have made it into the records, but they’re probably a better analogy.



  • IDK how idiomatic it still is, but I was taught to differentiate between Exceptions and Errors, where any recoverable Exception is to be logged and handled gracefully and only the truly unforeseen or fatal issues end up actually killing the execution.

    And for unforeseen errors, it’s kinda hard to construct a helpful error message, given you might not know just what info to include.

    (Of course, proprietary obfuscation adds another significant hurdle, but I suspect even without obfuscation, you might not be able to do much about closed-source code. That’s an argument against closed-source code, in my opinion, but I don’t think I need to preach to the choir here.)


  • The perpetual development cycle of attacks and defenses: weapons create a threat environment, which new armour technologies are created to protect against, which in turn new weapons are developed to circumvent. Virus begets Antivirus that has to keep up with new viral signatures. AI slop prompts AI detection tools and circumvention methods.

    So long as assholes continue to exist, anti-asshole-strategies will need to contend with their unwillingness to just fucking respect other people’s boundaries and wishes.








  • I’m the type to mess around with pipewire, break stuff, fix it, learn nothing from that and fuck it up again. I’ve got it doing what I want it to, and yet I wanna tinker around and probably mess it up again because I can’t seem to really understand the docs or configuration files.

    I’m the type to have two OS (Nobara, Ubuntu) on separate disks, then decide to rip the guts out of the second one (Ubuntu) and just use the disk for data storage (without reformatting) but keep forgetting to also delete the boot partition that no longer works anyway (because none of the system directories exist anymore) but occasionally UEFI randomly decides to boot it first and ends up with a fucked up and hopelessly confused GRUB.

    I’m the type to put the second disk in fstab, then unplug it and wonder why boot is having issues loading the filesystem.

    This is my primary system, so I’m just barely holding back from messing with the system itself, because I know I’ll fuck up something and I’d rather still have a working system to either troubleshoot from or at least decide I’ll postpone the unfucking and play Satisfactory instead to mess up my factory there.

    I’ll probably format my third disk again (currently Bazzite, which I never really fully set up to try at length) and try something new on there. Still haven’t figured out how to make my GRUB add entries for other disk, but also, I really don’t wanna touch my primary boot config.

    I can’t stop messing with things I don’t properly understand, get impatient with trying to understand the Docu and just fly blind, with predictable results. I tell myself half the joy is in fixing it, because the second it works, I forget it all and get to figure it out again next time.

    I’m the “incorrigible amateur” type.