• 12 Posts
  • 79 Comments
Joined 1 year ago
cake
Cake day: June 9th, 2023

help-circle





  • This is likely what happened. I think I’m gonna format the Windows SSD attached to the server (old install) and reinstall grub. Tomorrow, I guess. :(

    Edit: Now that I’ve had a moment to think, I realized that I deleted grub. It was on another SSD that I wiped. It was on the SSD that my old OS was on that I wasn’t using anymore. But my actual Linux install came from another computer. So when I dropped it in what became my server, I installed grub manually on the old SSD (which has now been wiped) to boot to my Linux SSD.




  • Obviously losing the third party apps and spez’s lies about the Apollo dev were the big ones, but honestly, I have had negative feelings towards the reddit community for a long time. Everyone is perpetually negative. They seem like miserable people. And the fact that every single comments section was same 3 fucking jokes repeated over and over and over. “I’m grieving my wife who passed away this morning” “I also choose this guy’s dead wife.” “Hahahahahahahahahahahahalolololoollolololol” “no it’s okay, the guy who the original joke is about thinks it’s funny, so it’s not offensive to say it to this guy.”





  • Not having to do a database rollback is a really, really hard problem to solve, and it would almost certainly need to be on the Lemmy developers side, not the server owner’s side. And if I’m them, that’s a low priority issue, and probably not something I even think about until 1.0.

    Basically, they write code that says what to do in the event of a database version change. Usually this only handles upgrade cases, because that’s what happening most of the time. One example of something you might do in a db upgrade is let’s say you had a column where the data type was only numbers, but now you want to allow any alphanumeric character for some reason. You could have a line of code that converts the number to a string.

    Okay, but now you need to go back to the previous version. Okay, your db change code runs, but it’s the old version of the db change code, not some new version that you wrote. You unfortunately didn’t have a crystal ball when you wrote this code and couldn’t predict that you were going to change the data to strings, so you didnt write code to change it from a string to a number.

    This is why most software doesn’t support downgrades unless you wipe first. For example, if you updated your aging MacBook to the latest Mac OS version, then realized it slows down your laptop too much, you can only go back if you first wipe your laptop in the process. So it’s just easier to just take a snapshot before an upgrade and revert to the snapshot if it fails. Some folks will even do “scheduled maintenance” time during the upgrade in which the whole system goes down for a short time so they don’t have to risk losing data that happened after the snapshot.


  • I learned about this http response code too late. About 4 years ago I was working at a startup and I was the “lead engineer” (aka only engineer) on a project where I had to design and implement an entire REST API. I really wish I would have put this in somewhere, since we weren’t doing code review (because it was literally only me).