[Bug]: Thumbnail links in playlists.db refer to the invidious instance used when adding the video, not to YT

[TheodorSmall]

Guidelines

• I have encountered this bug in the latest release of FreeTube.
• I have encountered this bug in the official downloads of FreeTube.
• I have searched the issue tracker for open and closed issues that are similar to the bug report I want to file, without success.
• I have searched the documentation for information that matches the description of the bug I want to file, without success.
• This issue contains only one bug.

Describe the bug

1. Use invidious API (preferably disable "fallback to secondary API") and select instance 1
2. Create a playlist and add a video to it
3. Optionally change the invidious instance to instance 2 and assume instance 1 is no longer working
4. In playlists.db, you will find that the thumbnail links are still pointing to instance 1, and therefore they depend on an instance that is no longer selected by the user.

Expected Behavior

The thumbnail links should point to YT, and dynamically the correct, current instance should be used to receive the thumbnail.

Issue Labels

accessibility issue, content not loading, inconsistent behavior

FreeTube Version

v0.21.3 Beta (pacman built from source)

Operating System Version

Artix Linux

Installation Method

.pacman

Primary API used

Invidious API

Last Known Working FreeTube Version (If Any)

unknown, probably none

Additional Information

No response

Nightly Build

• I have encountered this bug in the latest nightly build.

[TheodorSmall]

This also is a privacy issue, since the user may want to actively avoid using instance 1.

[efb4f5ff-1298-471a-8973-3d47447115dc]

I cant seem to find the identifier for the thumbnail links that are listed in the playlists.db. Are you sure you are talking about the right file?

[github-actions]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.