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
A lot of inspiration came from NewPipe and Invidious.
I created Piped to fix issues in NewPipe and Invidious which are architectural issues and cannot be fixed easily.
Invidious
Uses way too much resources.
Total bandwidth limited by the peak capacity of the load balancer.
Coded in Crystal, a language that is relatively hard for beginners.
Caching is done at a backend level.
Invidious was a learning project.
Invidious crashes all the time.
Various hacks are required to keep an instance running at a reasonable stability.
However, there are some drawbacks of Piped:
JavaScript is required
Browsers without Service-Workers support will feel significantly slower. Eg: Tor Browser
Yes, now yt-dlp just fetches the m3u8 playlist from the instance and connects to the youtube servers. Is it possible to proxify it like it is done in piped?
DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE
Checklist
Region
Any (to my knowledge)
Example URLs
Single video: https://piped.simpleprivacy.fr/watch?v=QwIlhuR_N2g
Playlist: https://piped.simpleprivacy.fr/playlist?list=PL8mG-RkN2uTx9Er8AqFDnD6mFvje5fybs
Provide a description that is worded well enough to be understood
This is a request to add support for the SimplePrivacy Piped Instance.
Provide verbose output that clearly demonstrates the problem
yt-dlp -vU <your command line>)'verbose': TruetoYoutubeDLparams instead[debug] Command-line config) and insert it belowComplete Verbose Output
The text was updated successfully, but these errors were encountered: