Add YouTube handlers about data-transfer-project

[upintheairsheep]

Additionally, if we use yt-dlp, should we require user authentication for exporting videos to prevent content theft, or is it better to leave it optional? A user could just remove the code associated with the antitheft system and steal all of MrBeast's content for instance, or do it manually, but at the same time the system could be default for services wanting to implement the system into their video sharing platform so it does not become part of the settings, and kids steal the content of every channel, or spammers initiating the system on a huge batch of accounts they do not own to create a content farm.

[lisad]

Thanks for the feedback! This is all rather important.

The most common DTP model is for each company - folks who have access to internal APIs, internal experts - to provide the extensions that do direct-to-platform export, and that seems like that would be easier for the Youtube folks to do than outside folks. You've provided some great tips for YouTube access points that might allow folks outside to build it anyway, but it would require a serious amount of bandwidth and at least some temporary storage, I expect.

The information about yt-dlp is very timely - I'm starting a repository of articles including how to do real server-to-server transfers but also what kinds of workarounds are sometimes available, that at least some people might want to use. See https://github.com/dtinit/portability-articles - I welcome your comments or contributions there