You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Because of YouTube banning IP ranges from various VPS services and patching out the Oauth2 method, people are currently unable to play YouTube links through their bots and thus making YouTube inaccessible until there is a workaround provided which while there are some that exist would probably just be a huge hassle for people that just want their bot to work without doing loops and hoops just to get it to work again
What is your ideal solution to the problem?
However, I really haven't seen anybody suggest so I'll go ahead and say it right now
Id really suggest using Invidious as an alternative to YouTube since it acts as a frontend for YouTube and there are plenty of services that use invidious as a service to play YouTube links without contacting Google/YouTube servers to do so, this also lessens the need to use stuff like IPv6 rotation or POtokens for the bot to function
How would this feature be used?
Users can use a invidious link from any of the instances currently available and then the bot will play the link through that
If the link happens to be a normal YouTube link, the bot will then convert the link to an invidious link from one of the instances available
If an instance is unavailable at the moment, the bot will switch to the closest instance that is currently available and play the link from there
Additional Info
Id would also like to mention that invidious has their API readily available for anybody to use right now so if any of the methods do not work anymore, we can at least switch to invidious and we can probably have a smoother experience from there
Checklist
I have checked the documentation to make sure this feature doesn't already exist
I might have to look for an alternative bot that I can host as I have been waiting for this bot to fix this issue for a while now. Yes I know it is not an easy fix but this bot is unusable without the ability to play music from YouTube etc. As this is it's only function.
I might have to look for an alternative bot that I can host as I have been waiting for this bot to fix this issue for a while now. Yes I know it is not an easy fix but this bot is unusable without the ability to play music from YouTube etc. As this is it's only function.
I might have to look for an alternative bot that I can host as I have been waiting for this bot to fix this issue for a while now. Yes I know it is not an easy fix but this bot is unusable without the ability to play music from YouTube etc. As this is it's only function.
Is your feature request related to a problem? Please describe.
Because of YouTube banning IP ranges from various VPS services and patching out the Oauth2 method, people are currently unable to play YouTube links through their bots and thus making YouTube inaccessible until there is a workaround provided which while there are some that exist would probably just be a huge hassle for people that just want their bot to work without doing loops and hoops just to get it to work again
What is your ideal solution to the problem?
However, I really haven't seen anybody suggest so I'll go ahead and say it right now
Id really suggest using Invidious as an alternative to YouTube since it acts as a frontend for YouTube and there are plenty of services that use invidious as a service to play YouTube links without contacting Google/YouTube servers to do so, this also lessens the need to use stuff like IPv6 rotation or POtokens for the bot to function
How would this feature be used?
Additional Info
Id would also like to mention that invidious has their API readily available for anybody to use right now so if any of the methods do not work anymore, we can at least switch to invidious and we can probably have a smoother experience from there
Checklist
The text was updated successfully, but these errors were encountered: