Plyr: Youtube prohibitions - We can't modify the Layout of Youtube Player, that's correct?

[renatog-cit]

Hello everyone how are you?

First of all congrats on the project! This library is very useful!

One question, we were reading this Google document about some prohibitions:
https://developers.google.com/youtube/terms/developer-policies#i.-additional-prohibitions

And in the 4th item there is:

modify, interfere with, replace, or otherwise disable any functionality, data, or content made available as part of, or in connection with, YouTube API Services. For example, you must not remove, obscure, alter, or disable any links that appear in YouTube players or in API Data.

6th item:

modify, build upon, or block any portion or functionality of a YouTube player;

And 10th

create, include, or promote features that play content, including audio or video components, from a background player, meaning a player that is not displayed in the page, tab, or screen that the user is viewing;

So just to confirm as a double-check in the "Legal" side we can't use Plyr to modify Youtube player that's correct?

I'm asking because I found nothing on GitHub about this item.

Thank you so much in advance.

[sampotts]

It has come up in the past. I'm in the process (slowly) of adding an option to disable the custom controls which solves 4th & 6th. It's in the dev branch but I've not fully tested it yet. 10th isn't something Plyr supports anyway.

[sparkktv]

Those terms only apply if you are using the API of YouTube Services. Meaning building an app or building something that requires their API code or API key. And in that case you could just disable Plyr in those applications once the disable option is available.
And there are ways around that but you'd have to deep dive search to find those ways.
And the end of the day it's really that YouTube just wants their name on your own stuff if you are using their services to host your video. They want credit basically. And they know they can't stop you unless you are using their API which they have to approve, it's a bully-tactic in my opinion but if you can avoid their API, you're good...