Here is an example:
https://www.youtube.com/embed/YzoOf0jLqUM

When substituting "www.youtube.com" with "tube.cadence.moe" I merely get a 404 error.


Another example:
https://www.youtube.com/watch?v=YzoOf0jLqUM&feature=emb_imp_woyt

This does redirect, but to a full CloudTube page, rather than an embedded video page, like YouTube, most Invidious instances, and Piped do.

Ah, I see, awesome.

The ideal behaviour would be to just display the video alone, but
unfortunately, we don't live in a perfect world. What do you think it
would be good to do if there is an error in extraction? What about if
everything seems to work fine from the server's perspective, but the
video is actually unplayable in the browser? It would be disappointing
if there was no way to get to YT from the embed.

I'm not sure how I should design this at the moment.

Regarding the extraction, I have yet to learn enough in order to be able to give a suggestion in this case, however you might be able to think of something by looking at how many Invidious instances, or how Piped, go about this.

Regarding testing, I am willing to be a guinea pig for this, and test and report anything userclient-side.






On Monday, August 16, 2021, 10:07:48 AM UTC, Cadence Ember <cadence@disroot.org> wrote: 





Ah, I see, awesome.

The ideal behaviour would be to just display the video alone, but
unfortunately, we don't live in a perfect world. What do you think it
would be good to do if there is an error in extraction? What about if
everything seems to work fine from the server's perspective, but the
video is actually unplayable in the browser? It would be disappointing
if there was no way to get to YT from the embed.

I'm not sure how I should design this at the moment.