You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when synchronizing a channel, metadata like playlists, banner, avatar from the remote channel/platform are not being synchronized.
Describe the solution you would like
Similar to #5186 periodically pull for metadata changes from the remote platform. This data is exposed via yt-dlp when not using --flat-playlist.
The data will be excessively large, reaching multitudes of tens of megabytes on large channels. Thus the YoutubeDLCLI.getInfo function will need to be changed (or a new function introduced) to buffer to storage instead and to expose the data via a stream interface to not cause excessive memory usage.
To not overexhaust platform specific API's yt-dlp will call, this data should only be retrieved after initial synchronization and videos import, and then on a daily basis.
yt-dlp supports passing some platform specific tokens to reach beyond those limits, supporting those would aid users that wish to decrease that time window.
Store a local BLAKE2b hash for each of the playlist, banner and avatar synchronized metadata, compare this hash during periodical pull of remote metadata and modify the locally stored metadata if they don't match.
The text was updated successfully, but these errors were encountered:
Describe the problem to be solved
Currently when synchronizing a channel, metadata like playlists, banner, avatar from the remote channel/platform are not being synchronized.
Describe the solution you would like
Similar to #5186 periodically pull for metadata changes from the remote platform. This data is exposed via
yt-dlp
when not using--flat-playlist
.The data will be excessively large, reaching multitudes of tens of megabytes on large channels. Thus the
YoutubeDLCLI.getInfo
function will need to be changed (or a new function introduced) to buffer to storage instead and to expose the data via a stream interface to not cause excessive memory usage.To not overexhaust platform specific API's
yt-dlp
will call, this data should only be retrieved after initial synchronization and videos import, and then on a daily basis.yt-dlp
supports passing some platform specific tokens to reach beyond those limits, supporting those would aid users that wish to decrease that time window.Store a local BLAKE2b hash for each of the playlist, banner and avatar synchronized metadata, compare this hash during periodical pull of remote metadata and modify the locally stored metadata if they don't match.
The text was updated successfully, but these errors were encountered: