Replies: 1 comment 3 replies
-
|
Feature requests belong at https://features.jellyfin.org |
Beta Was this translation helpful? Give feedback.
-
|
I do plan to implement this feature @thornbill - I'm looking for technical discussion on implementation details as I've already started looking into this, but I've also spun up a feature request to track it over there as well https://features.jellyfin.org/posts/3012/jellyfin-web-offline-viewing
|
Beta Was this translation helpful? Give feedback.
-
|
Technical discussion are usually held here https://github.com/jellyfin/jellyfin-meta/discussions |
Beta Was this translation helpful? Give feedback.
-
|
@sjorge But both the features site and the readme in that repo state that discussions for the individual components are to be held in their respective repos; this is a change specific to the operation of the web client
Have the project's rules around technical discussions changed? |
Beta Was this translation helpful? Give feedback.
-
Re feature request: https://features.jellyfin.org/posts/3012/jellyfin-web-offline-viewing
Enable offline browsing of libraries/viewing of content downloaded from a Jellyfin server. I've been contemplating this feature for a while now and I think the web standards have finally caught up to a point where it's feasible. A combination of persistent storage APIs like StorageManager and IndexedDB allow browser apps to finally store substantial amounts of data on the orders of GBs/TBs. It also seems to me that there's no technical barrier downloading transcoded media over the raw media for smaller file sizes on device. A queuing system would likely need to be implemented client-side though to not overload the server with download requests.
https://developer.mozilla.org/en-US/docs/Web/API/Storage_API/Storage_quotas_and_eviction_criteria#does_browser-stored_data_persist
Beta Was this translation helpful? Give feedback.
All reactions