| ▲ | xp84 6 days ago | |||||||||||||||||||||||||
I seem to remember this stupid behavior with maxresdefault going back at least a decade. As though there is no way that it could default to the correct thumbnail for any video -- surely it would not just help random hackers like OP, but also be more efficient for internal teams at Google to be able to render a preview for a video knowing only its ID, instead of making an API call to get the correct thumbnail name. Great example of a 10-minute bug being prioritized at #837,434,212 and never resolved. I'd like to judge harshly, but let's be honest, most codebases older than a month have their share of these embarrassments. | ||||||||||||||||||||||||||
| ▲ | cubefox 6 days ago | parent [-] | |||||||||||||||||||||||||
That reminds me of another YouTube embarrassment: Some ten years ago, Facebook added a "translate" button to every comment. The translations were pretty bad (they used Bing Translate rather than the much better Google Translate), but it was really useful to understand people from all over the world. You would think YouTube (owned by Google) would in short order also add such a button to comments. Haha, no. They didn't. About a decade later, probably more, they finally implemented it, albeit only in desktop mode. Not a big deal, just millions and millions of unreadable comments for millions of users for many years. Was probably prioritized at #837,434,211. | ||||||||||||||||||||||||||
| ||||||||||||||||||||||||||