• 0 Posts
  • 144 Comments
Joined 9 months ago
cake
Cake day: June 4th, 2025

help-circle


  • I guess it depends on the containers that are being run. I have 175 containers on my systems, and between them I get somewhere around 20 updates a day. It’s simply not possible for me to read through all of those release notes and fully understand the implications of every update before implementing them.

    So instead I’ve streamlined my update process to the point that any container with an available update gets a button on an OliveTin page, and clicking that button pulls the update and restarts the container. With that in place I don’t need fully autonomous updates, I can still kick them off manually without much effort, which lets me avoid updating certain “problematic” containers until after I’ve read the release notes while still blindly updating the rest of them. Versions all get logged as well, so if something does go wrong with an update (which does happen from time to time, though it’s fairly rare) I can easily roll back to the previous image and then wait for a fix before updating again.






  • It’s an MoE (Mixture of Experts) approach. An 80B-A3B model has 80B parameters total, so that dictates the size of the model and the VRAM+RAM you need to have to hold it, but only 3B of those parameters are active at any given time. This reduces the intelligence of the model compared to an 80B dense model, but improves the speed. In the end it’s the size of an 80B model, with the intelligence of a ~40B model, that runs at the speed of a 3B model.

    Pretty much all state of the art models either have already, or are in the process of switching to an MoE design, since it significantly reduces the hardware required to run big models at usable speeds. You can often get usable speeds on MoEs without a GPU at all.



  • self-signed won’t get rid of any warnings, it will just replace “warning this site is insecure” with “warning this site uses a certificate that can’t be validated”, no real improvement. What you need is a cert signed by an actual certificate authority. Two routes for that:

    1. Create your own CA. This is free, but a PITA since it means you have to add this CA to every single device you want to be able to access your services. Phones, laptops, desktops, etc.

    2. Buy a real domain, and then use it to generate real certs. You have to pay for this option ($10-20/year, so not a lot), but it gets you proper certs that will work on any device. Then you need to set up a reverse proxy (nginx proxy manager was mentioned in another post, that will work), configure it to generate a wildcard cert for your domain using DNS-01 challenge, and then apply that cert to all of your subdomains. Here’s a pretty decent video that walks you through the process: https://m.youtube.com/watch?v=TBGOJA27m_0


  • I use the Turtle Beach Stealth 700 Gen 3

    I really like them. You can connect 2 different RF sources (USB dongle) as well as bluetooth and can even use RF + bluetooth simultaneously. This is great for example when gaming on my PS5 with them (using the USB dongle) while they’re also paired to my phone over bluetooth. Call comes in and I can answer directly (mic will switch over to BT) and hear both the game and the call at the same time. Hang up the call and the mic switches back to the RF source.

    Anyway, I have one RF dongle in the PS5, the other RF dongle in my gaming desktop, and bluetooth connections to both my Linux laptop and my phone, so I can use any or all of them with the same set of headphones without changing anything.