- 3 Posts
- 4 Comments
Joined 5 months ago
Cake day: June 5th, 2025
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
barnaclebill@lemmy.dbzer0.comOPto Selfhosted@lemmy.world•Must my Jellyfin server be able to transcode AV1 videos?English1·12 days agoVery good point, thank you for chiming in.
barnaclebill@lemmy.dbzer0.comOPto Selfhosted@lemmy.world•Must my Jellyfin server be able to transcode AV1 videos?English2·12 days agoGood point, and I agree - after reading all the responses, I’m leaning toward spending the few extra bucks so that I don’t have to fret all the potential scenarios that might require transcoding.
barnaclebill@lemmy.dbzer0.comOPto Selfhosted@lemmy.world•Must my Jellyfin server be able to transcode AV1 videos?English3·12 days agoI’ll double check my various devices’ specs before I move forward. Thanks for confirming that.
Thanks for the idea about exporting torrent data using the CLI - I’ll look into that. Re: linking, I currently use sym links to avoid duplicating storage across multiple trackers. My main reason for sym links is so I can link across different devices (my understanding is hard links are limited to the same device). If I understand correctly, hard link or sym link aside, the problem is for a given torrent, I don’t want to delete it from any trackers if it’s performing on at least one of them. My thought process is if I’m keeping the content around for even just one of my trackers, I may as well keep cross seeding it, if for no other reason than to earn that sweet bon. The hard part is identifying which torrents are performing poorly across all trackers. If I can get the data into CSV format, then I think I can massage it well enough to tell which (poorly performing) torrents can safely be purged from all trackers.