• 0 Posts
  • 23 Comments
Joined 9 months ago
cake
Cake day: February 15th, 2024

help-circle
  • I’d recommend against it. Apple’s software ecosystem isn’t as friendly for self hosting anything, storage is difficult to add, ram impossible, and you’ll be beholden to macOS running things inside containers until the good folks at Asahi or some other coummity startup add partial linux support.

    And yes, I’ve tried this route. I ran an m1 mac mini as a home server for a while (running jellyfin and some other containers). It pretty consistently ran into software bugs (less maintained than x64 software) and every time I wanted to do an update instead of sudo whateveryourdistroships update, and a reboot, it was an entire process involving an apple account, logging into the bare metal device, and then finally running their 15-60 minute long update. Perfectly fine and acceptable for home computing, but not exactly a good experience when you’re hosting a service.





  • Ptsf@lemmy.worldtolinuxmemes@lemmy.worldOK, which one of you is it
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    29 days ago

    You literally cannot mess with your emissions system legally… nor can you disable or modify certain safety systems (seat belts, etc). Software that goes into vehicles requires validation testing. You might be fine doing 1 off things, but there will never be a “flash able” car on the market that let’s you bring your own software, and honestly I’m good with that. I don’t need your massive multiple ton machine bluescreening down the highway or locking up the breaks randomly because you installed the wrong module.




  • If you have an old desktop to repurpose, jellyfin is best ran on one of those with an Intel a380 gpu as long as the motherboard supports resizable bar. Cpu-wise jellyfin doesn’t really do anything intensive, and intel’s gpus all come with the same 2x video pipelines so upgrading to a 770 wouldn’t add any performance. If you’re buying new, my recommendation would be to get one of those intel white label laptops xpg made for a while. They can be had around $300-500 and come with a intel arc gpu you can use for encoding, resizable bar, decent ram, and a decent cpu. Great little jellyfin boxes.



  • If it’s time, storage, and compute sensitive to generate it beforehand why on this green earth would you want to do it at stream runtime? Do you enjoy the thought of waiting 5-10 minutes for a stream to start or causing continual buffering problems during the stream? Also to my understanding the way it is built requires that the encoding be done for the entire length of the stream before any benefits are shown, so starting the process at stream launch would be less than useful even under the best circumstances. I think what you want to do is to sort your library into two, one you want to watch, and an archive. From there you can enable trickplay on just the “want to watch” library.










  • Yeah! The practice is called drive shucking (kinda like Oysters) and you just need to be considerate of the limitations. The drives often end up cheaper, but lose warranty support once they’re shucked. They’ll also occasionally be slower than a normal drive or have an odd connector, but that is rare since it’s usually cheaper to go with something ‘off the shelf’. If you Google it though you should usually be able to find the handful of drive SKUs they’ll use in whatever external you’re planning to shuck.