It's still here for me, it could be blocked on your instance
I'll edit my post if he replies to me
They'd get into an endless loop of responding to each other. Just a regular internet conversation then
Needed one the other day because the post only had the Piped one and Piped never loads for me. When it briefly used to load then it would buffer constantly.
Hot take: Piped API sucks and is a giant waste of resources (unless you're running your own instance)
What does that have to do with the API though? You said that the API sucks I'm curious about that part. I understand thinking the public instances suck because they can never keep up and get overloaded but your original comment said that the API itself was bad somehow.
Content creators get almost nothing from ads. You're better off donating $5 to their buymeacoffee or patreon or similar, etc.
That's not true and I don't know where this comes from. Ask anyone who actually is successful on YouTube and they will tell you YouTube ads pay quite well and their revenue share is very favorable.
actually, both use the newpipe extractor https://newpipe.net/FAQ/download/#download-youtube-api https://docs.piped.video/docs/architecture/
That's great for mobile. Desktop I don't like using piped.video because it's ugly and slow so I just grab link from there then use yt-dlp + mpv.
What is the etiquette for posting YT links in this scenario? If the content is from YT I'd prefer to post the canonical link instead of a mirror that may go down or may get hugged to death. If you'd rather view on a mirror I'd suggest you use e.g. LibRedirect. Does this make sense? Are there better ideas? I'd like to promote non-YT frontends but am not sure what the best option here would be.
Piped is not a mirror, it's just like a backdoor access to the original YouTube video.
So if you can access it on YT, you can access it on Piped
Piped can't die. It's just software. Maybe one instance can "die" and go offline for some reason but there are thousands more.
Same for Invidious.
