• 0 Posts
  • 23 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle
  • He bought it because he couldn’t stop being an arrogant edgelord keyboard shit-talker, and he accidentally made himself personally legally liable doing so. The Twitter board called his bluff, seeing the most amazing opportunity to rid themselves of an expensive and slowly dying company, and Musk had already pissed off the SEC (or one of the other financial government services) enough that he was at risk of having his finances in other companies audited.

    So he was forced to buy it because he’s an impulsive troll. Everything else since then is pretty incidental, and unsurprisingly dripping with hypocrisy like this.


  • This forces my team to find creative ways to keep them working while also taking measures to isolate them as much as possible. I also use them to teach old exploits that have been patched in more recent versions, walking people through how it worked and why it existed.

    I am interested in learning more about this. I know a fair bit about networks but exploit history and modern attack / defense strategies and server hardening are not my main specialty. Do you have any good links or resources that you can share?



  • Excellent, thankyou! I was just going to throw ubuntu at it unless I really needed something else because of the potato specs, so hopefully drivers are already sorted.

    especially the WiFi/Bluetooth chipset

    Noted. I would be pissed to not have that working.

    Don’t try anything fancy

    No chance, I’ve been burnt by my unix arrogance enough times to not want to try it on proprietary hardware. Until now I assumed even getting Linux on there was too fancy, I still remember other people fighting for weeks with their hackintosh a decade ago.










  • Different tasks. VSCode is littered with half-baked spaghetti code from various projects. My terminal window is for system-level non-project interactions.

    I stick with terminals and vi for various day-to-day administrative things, because you never know when you’ll have to log into a different machine which doesn’t have all your software and preferences set up. I would prefer not struggle to recall keyboard shortcuts I last used 100 years ago when that happens.

    It’s bad enough having ADHD and long covid to completely obliterate my working memory, without the added irritation of googling “man vi move to section”, knowing you have definitely used the command many times in the past.


  • It’s not possible to remove bias from training datasets at all. You can maybe try to measure it and attempt to influence it with your own chosen set of biases, but that’s as good as it can get for the foreseeable future. And even that requires a world of (possibly immediately unprofitable) work to implement.

    Even if your dataset is “the entirety of the internet and written history”, there will always be biases towards the people privileged enough to be able to go online or publish books and talk vast quantities of shit over the past 30 years.

    Having said that, this is also true for every other form of human information transfer in history. “The history is written by the victors” is an age-old problem when it comes to truth and reality.

    In some ways i’m glad that LLMs are highlighting this problem.




  • Part of this is a symptom of support demands from users. There has been an expectation in software development historically, back from when software was always hideously expensive and limited to companies as users, that errors would be fixed by someone on demand ASAP. We’re all familiar with the IT guy “file a ticket first” signs on offices, or the idiot executive’s demands for a new computer because they filled theirs with malware somehow.

    But now a lot of what software did is web-based and frequently free/freemium. But the customer’s expectations of having their issue fixed ASAP remains. Despite the internet being far from a standardised system of completely intercompatible components. So updates and fixes need to continually be deployed.

    And that’s great for most people, until that expectation extends to the creation of new features, from management and end users alike. Then things start getting pumped out half-finished-at-best because you can just fix the MVP later, right?

    We’re going to get to the backlog sometime… right? We don’t need to keep launching new features every quarter… right?