• 0 Posts
  • 133 Comments
Joined 3 years ago
cake
Cake day: October 1st, 2023

help-circle
  • Yeah. It’s a betrayal of trust in my eyes. They were the first company to get a genuine “plug-and-play” experience to 3D printing. They amassed a huge user base, then acted against those users’ rights. There’s no way in hell they win the lawsuit against them, so at least the people who have already bought printers from them should still be able to use them. But I would avoid Bambu like the plague from here on.




  • Same. The devs get big bonuses if the game is successful, so I bought the game. If the publisher won his lawsuit, I would have pirated it. If they ever take the game away, I’ll pirate a copy. Obviously I’m emotionally invested in the devs getting what’s rightfully theirs, but I also don’t see an issue with piracy of big name games in the modern age of gaming. But please buy indie games if you can afford to, they are the only ones keeping gaming alive right now












  • Don’t change now if you don’t have an issues in my opinion. However, if you have the space for the jellyfin backup, it should be a pretty simple transition. I always prefer deploying using docker compose for all my services, I have backups of the compose files, and it handles all the networking between all the services (VPN, *arr stack, qbt, seer, jellyfin) When I had to move off of my ancient server after it kicked the bucket, it was as simple as copying my compose files, a single docker deployment per stack, and loading the backups for specific services. I’ve not had any issues with Jellyfin on docker, but I am using GPU passthrough to allow for hardware accelerated transcoding.