-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
[Feature] invidious/piped as backend #293
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This is not a good option, as it would require choosing an instance. That means that if the instance is far away, music will have a lot more buffering. Also, if the instance went down, then Spotube will stop working. Most Invidious/Piped instances experience regular downtime. It will generally result in worse UX. If you are concerned about privacy, you should use a VPN. |
You can add a drop menu for either of invidious or piped. So if the instance is down, the user can select something else. |
First of all, Spotube doesn't send any kind of data to YouTube at all Secondly, indevious and piped both aren't reliable. I can add certain amount of instances in instance list but there's big chance all of them can die (at once except the official one) as mentioned by @IntoTheVoid-900 Finally, time. It's already a huge overhead for Spotube to go and search on YouTube for the Spotube track and algorithmically rank and match the appropriate one. So IMO, there's no space for any extra latency |
You had me at
Thanks for the details! |
Wouldn't it be nice if I can choose to play songs via invidious/piped?
I use spotube to escape from spotify and stop it from eating my data but now I have to face yt (google) with my data so it would be nice to use invidious or piped instead! so I can save my data from spotify and yt
The text was updated successfully, but these errors were encountered: