Replies: 2 comments
-
Thank you for the suggestion! I’ll definitely consider this. However, my primary concern is that implementing this feature would require Yamtrack to store Jellyfin credentials in a way that allows reversible encryption, which poses a potential security risk. Ideally, I’d prefer to avoid storing passwords entirely. I’ll explore the Jellyfin API to see what options are available for filtering watched items and other relevant data. For reference, here are some links for myself that might be helpful for implementation: |
Beta Was this translation helpful? Give feedback.
-
Yamtrack is getting really big, and maintaining it and adding all the features is surely taking a lot of your time. Maybe it's time to start a $$ bounty for time consuming features? I'd gladly chip in for Jellyfin integration via API/dedicated plugin instead of webhooks |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Currently, Jellyfin integration works by setting a webhook. In a multi user setup, each user has to request a Jellyfin admin to setup their webhook. (and Jellyfin webhook UI is terrible right now TBH)
Would it be possible to have a self-serve integration ?
I've seen Ryot doing a Jellyfin import with user/password. It's an import and not a real sync/in-progress tracking. Paired with a scheduled job, it could sync watched items. The trade-off seems ok to me, considering it would be self-serving.
Beta Was this translation helpful? Give feedback.
All reactions