-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
[Feature Request] Alternative to Youtube Front End #108
Comments
I disagree. As far as I know, Invidious does not require JavaScript, whilst Piped does. Anyhow, that does not matter. I'll look into supporting Piped later today. |
Oh! i see, its true, piped requires javascript, i'm more saying about the system itself, i think as a user it works better, at least for me. I'm gonna look more into this. |
Since piped uses the same URL format as both youtube and invidious, you should be able to use it in the youtube frontend field in the settings: ie |
Yes, that's true, but I don't know - and that was what I wanted to test - if the search works without JavaScript, because to my knowledge, php-curl does not execute JavaScript. |
thats correct, php-curl simply fetches documents over http, without running any javascript. Using piped as a youtube frontend for redirection shouldn't make much difference, since the target pages will be opened on the user's client. However as for getting video search results, I don't think there is much reason to be using piped over invidious. When #81 is implemented, it should offer a better solution than relying on a third-party frontend for search results. |
i've looked around and there is lighttube as well, but does use javascript too, so nothing too much different. |
Of course, I understand, but I was wondering if Piped uses JavaScript to make requests to get queries or not. That's what I wanted to check. |
No, because it's not added to the trusted proxy domains. That might be a good way to fetch thumbnails though! |
https://docs.piped.video/docs/api-documentation/#streamsvideoid But why? It's a backend change, so it makes no difference in what the user experiences. One can already used Piped as a frontend as explained here.
It could reduce some load on the instance used, but if that's the goal then we should be focusing on #81. Even Invidious uses the YouTube API for its search. |
As of the latest commit (at time of writing), we use YouTube directly (proxied of course) for the thumbnails, which also makes it so that Piped or other instances should fully work! |
I've been using LibreY for some days, but i don't use invidious, instead I've been using piped.video, its way better than invidious, I've looked around here in issues and not found someone asking this question, so I've made it.
The text was updated successfully, but these errors were encountered: