• 0 Posts
  • 310 Comments
Joined 3 months ago
cake
Cake day: December 13th, 2024

help-circle









  • I had the same experience with my parents. They have a Samsung TV and the Jellyfin experience was awful.

    I ended up getting them a little N100 mini pc and installed Bazzite and the Jellyfin app from Flathub. You can configure it so it knows it’s on a TV, and responds to keyboard controls. I got them a remote from a company called Pepper Jobs that gives keyboard input and now they have a great experience with it. Even my mom, who’s a big technophobe, loves it.

    My dad also has an LG TV in his workshop that doesn’t have a working Jellyfin app (cause it’s ten years old), and he uses the Jellyfin app for his Xbox on that one.





  • If it’s a mobile app, the operating system handles crash logs, and reports them to you through your app management portal. Then for connection issues to the host or handled errors, you can store that in your app’s data store, and upload them once connection is restored.

    If it’s a web app, you can save them in local storage through your service worker, then upload them once the connection is restored. If you don’t have a high level error handling function on your web app, that’s an issue with your web app, not your logging infrastructure.

    For a network outage error, these aren’t usually reported if the problem is on the client side, since that’s not something we can do anything about. Both mobile apps and service workers can tell if the operating system is disconnected from the network. If it’s an issue connecting to our host (host is unreachable, but network is online), that’s when we’d save the issue and log it later once service is restored.

    We can tell when our services go offline, because we have health checks on our hosts. So, technically, we don’t need client side reporting if our hosts are down. But, every place I’ve worked at has had them anyway.

    Analytics don’t usually run on the same hosts as services, so if your service goes down, that doesn’t mean your analytics platform is down. I mentioned before how many systems there are in big tech services. Analytics is one of those systems. It’s generally completely separate from user facing services.






  • Absolutely yes. It’s better to use an old PC for a home server, because upgrades are cheaper, parts are easier to find, troubleshooting is generally easier, they’re usually more energy efficient than an older dedicated server, and you’re saving an old pc from becoming e-waste.

    That being said, what you want to run on it determines how old/cheap of a PC could work for you.

    Jellyfin works best when you can do hardware encoding, and these days that means throwing an ARC A310 in there and calling it a day. If you have a new enough processor, you don’t even need the graphics card.

    Mastodon is pretty disk heavy, but if you’ve got a nice hard disk to put the Minio server on and an SSD for the db, you’re golden. That’s how I run https://port87.social/. It’s running on an old 6th gen Intel i7. The PC I built in 2015 (with a few upgrades).

    CPU intensive servers like Minecraft are where you start to run into problems with older hardware. If it’s just you on there, a 10 year old CPU is fine, but if you’ve got a few friends, the server may start to struggle to keep up. I had to move my server off that same system I talked about above, because Minecraft was pegging the CPU a lot. But a 5 year old CPU would be fine for that. (Assuming that the 10 year old and 5 year old CPUs were both top tier CPUs when they were new. Like i7, i9, Ryzen 7, Ryzen 9. A five year old i3 would still struggle.)

    Basically unless you’re trying to run AI models on it, cheap hardware is fantastic for personal servers.