It would be stupid, but very funny if someone created a YouTube bot for Piped links…
They’d get into an endless loop of responding to each other. Just a regular internet conversation then
Like when the reddit lotr bots get stuck in a loop.
Just post piped links then loser.
It’s a thankless job
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
So if you can access it on YT, you can access it on Piped
Unless Piped dies
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.
Oh, I thought it’s a single website. My bad
The bot OP is talking about links to a single website. But the code running the site is used to run many sites like it. Similar to how Lemmy works.
That’s my understanding, anyway. I haven’t looked too much into it, so I could be wrong.
Do content creators get views if I watch a video through any of the front-ends?
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.
Hot take: Piped API sucks and is a giant waste of resources (unless you’re running your own instance)
What is it exactly?
It’s a proxy to access YouTube privately. But all the servers are overloaded.
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.
I agree. I’ve had to switch instances so many times, it’s frustrating.
