> I wonder how they use these feeds if that's only internal.
Perhaps they don't, it could be that the interface was written to a more flexible spec to allow for ongoing changes, and close to release they decided which features would be officially supported. In that case the method being used here is either deliberately kept around for potential future use, or is a bit of their tech debt.
It may also be something that is internally supported still because it is used in legacy apps that are still out there (some smart TVs have ancient apps and no upgrade path) but they don't want it used by new code as it will eventuality be removed.
In any of those cases, there is no guarantee it'll still be there tomorrow.
I was annoyed one day and was looking online around for some solutions.
You can find a bit more information here: https://stackoverflow.com/questions/71192605/how-do-i-get-yo...
Thanks!
From your link:
> However, this pattern was found by me by acquiring all playlists from "UUAA" to "UUZZ" and is not officially announced by YouTube.
Okay, this was reverse engineered and there's no promise from Google on that :-)
I wonder how they use these feeds if that's only internal.
> I wonder how they use these feeds if that's only internal.
Perhaps they don't, it could be that the interface was written to a more flexible spec to allow for ongoing changes, and close to release they decided which features would be officially supported. In that case the method being used here is either deliberately kept around for potential future use, or is a bit of their tech debt.
It may also be something that is internally supported still because it is used in legacy apps that are still out there (some smart TVs have ancient apps and no upgrade path) but they don't want it used by new code as it will eventuality be removed.
In any of those cases, there is no guarantee it'll still be there tomorrow.
Then again, supported APIs from Google have exactly the same guarantees.