Essentially what I'm propossing is a different implementation of "Data Fetch Timeout". Where instead of not displaying the title/thumbnail until the API request finishes, it displays the originals. This would likely be best as an additional option, likely with it's own much shorter timeout (to avoid fickery loading, where the api response is followed very shortly after displaying the originals), and of course to enable those users that under no curcumstances want to see the clickbait titles/thumbnails to disable this entirely.
Why?
This is mostly useful when the servers are slow/temporarily offline as it can cause pages to become unusable until the fetch timeout, especially if the user makes use of the online thumbnail replacement feature as well. Shortening the fetch timeout mostly solves this issue already for when the servers are offline, but also causes the extension to not function when the servers are temporarily slower than usual, or can become unreliable on less reliable internet connections.
Essentially what I'm propossing is a different implementation of "Data Fetch Timeout". Where instead of not displaying the title/thumbnail until the API request finishes, it displays the originals. This would likely be best as an additional option, likely with it's own much shorter timeout (to avoid fickery loading, where the api response is followed very shortly after displaying the originals), and of course to enable those users that under no curcumstances want to see the clickbait titles/thumbnails to disable this entirely.
Why? This is mostly useful when the servers are slow/temporarily offline as it can cause pages to become unusable until the fetch timeout, especially if the user makes use of the online thumbnail replacement feature as well. Shortening the fetch timeout mostly solves this issue already for when the servers are offline, but also causes the extension to not function when the servers are temporarily slower than usual, or can become unreliable on less reliable internet connections.