snuffyDev
[FEAT] support for youtube query parameters
Is there a reason for changing query parameter names? i.e: using listen?id= instead of watch?v=.
All open source front-ends tend to use the original API interface as the proprietary front-end for quick switching (by replacing the base domain part for example) between the two, or at least have the proprietary one as a fallback. For example, https://youtube.com/watch?=XXXXXX can easily be viewed in invidious instance by replacing base domain with yewtu.be to get: https://yewtu.be/watch?=XXXXXX.
The original reason for the change in paths was mostly just down to semantics (Beatbump does audio only, so watch didn't make as much sense) however supporting the standard routes is on the final todo list for this refactor I've been writing. Thanks for the reminder!
