Add YouTube handlers

[upintheairsheep]

Hello, YouTube is a huge service, and due to it, many people would want to become YouTube expats for various reasons, such as a lack of a certain feature that only another service includes, or if not leaving, some users would want to use the DTP to copy all of their YouTube content to another platform to increase potential audience or backup their videos in case of account termination.

YouTube currently has lots of types of data to implement for export, such as the videos themselves, the video metadata, the video captions, and community posts, which could be exported as social media posts, and possibly comments which could be converted to social media posts with the original YouTube URL preceding the comment text.

The export handle could either be created by the hands of Google employees, which could find the original upload format in it's original form, or another approach is to use yt-dlp to download the videos, their thumbnails, their captions, and their metadata with different homemade scripts for community posts and comments due to them being out of the scope of yt-dlp, and possibly a system to probe for private and unlisted videos that would otherwise not be detected by yt-dlp. The import module should basically only support the upload of videos and the creation of community posts.

Also, to mention I personally have a friend who fears getting his account terminated due to recent false copyright strikes, and because of it, has set all 8000+ of his iOS and macOS gameplay videos to private indefinitely, and thinks reuploading all of the videos would be tedious and therefore has the majority of his videos lost indefinitely until a solution is done to transfer private videos.

[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