[GDjkhp]

No description provided.

[GDjkhp]

some videos doesnt provide maxresdefault.jpeg and returns 404. let me know if should i write a parser for the following:

https://img.youtube.com/vi/<insert-youtube-video-id-here>/hqdefault.jpg
https://img.youtube.com/vi/<insert-youtube-video-id-here>/mqdefault.jpg
https://img.youtube.com/vi/<insert-youtube-video-id-here>/sddefault.jpg
https://img.youtube.com/vi/<insert-youtube-video-id-here>/maxresdefault.jpg

[GDjkhp]

ok nvm if i do that, it will cost one request per song and if i have 1000+ song playlist, its terrible 💀 keep it maxresdefault

[1Lucas1apk]

I think we should keep mqdefault.jpg as the default on the NodeLink side. maxresdefault.jpg isn't available for every video, and this can be demonstrated with an actual example:

• [maxresdefault.jpg](https://i.ytimg.com/vi/jNQXAC9IVRw/maxresdefault.jpg) — returns HTTP 404 according to this [measured comparison](https://charj.it/blog/youtube-thumbnail-urls).
• [mqdefault.jpg](https://i.ytimg.com/vi/jNQXAC9IVRw/mqdefault.jpg) — available at 320×180 for the same video.

The issue is that this change only switches the default URL; it doesn't check whether the higher-resolution thumbnail actually exists. That means videos can end up with a missing thumbnail even when a lower-resolution one is available.

I think this would be better handled on the client side, such as in the bot, if higher-resolution thumbnails are needed there. That way, NodeLink can keep its current default behavior instead of changing the thumbnail URL for every consumer.