4 ms·

Is this problem actually solvable? As in, does YouTube expose an API for doing the things you're talking about? If not, then there's really not much anyone can

Is this problem actually solvable? As in, does YouTube expose an API for doing the things you're talking about? If not, then there's really not much anyone can do about it.

Jugurtha 6y ago
>Is this problem actually solvable? As in, does YouTube expose an API for doing the things you're talking about? https://developers.google.com/youtube/v3 https://developers.google.com/youtube/v3 The description from the above link: With the YouTube Data API, you can add a variety of YouTube features to your application. Use the API to upload videos, manage playlists and subscriptions, update channel settings, and more. >If not, then there's really not much anyone can do about it. If their API is unusable, then follow the steps in the documentation, only let a computer do it. Use OAuth to authenticate with the service, access user's content that may be public, private, or unlisted. On a user operation, say move videos from one account to the other, in the backend: download the videos to temporary files using a third party tool that I will not mention here, then upload them to the new account. If you want to skimp, mount the user's Google Drive account to store the videos temporarily (as a buffer), and then from their Google Drive to their YouTube account. This way you don't pay for storage and are scalable right off the bat. Then build everything on top of Google App Engine : D Except you'll have a harder time doing the mount operations if you're on GAE, I suppose. So you only receive requests, mount Google Drives, download videos there, then the videos to the user's account/channel. Yes, you could eventually use something "in-memory", but if you have a lof of requests, you'll have to account for that RAM, hence using the user's Google Drive account. Again, I'm thinking of this off the top of my head, but I think it checks out. The user only has to select the videos from the source, and choose a destination, click OK, done. Go for coffee or something, instead of downloading them and good luck for people with crappy internet to do that. Future versions may enable you to do CRUD on the videos on a usable interface, not like the Studio thing. Display accounts and channels and playlists like folders and move videos around like you'd do on a file explorer, etc. I may do that once to transfer my videos. Your bio is "Serial Side Project Maker"... :P

Is this problem actually solvable? As in, does YouTube expose an API for doing the things you're talking about? If not, then there's really not much anyone can do about it.

Jugurtha 6y ago

>Is this problem actually solvable? As in, does YouTube expose an API for doing the things you're talking about? https://developers.google.com/youtube/v3 https://developers.google.com/youtube/v3 The description from the above link: With the YouTube Data API, you can add a variety of YouTube features to your application. Use the API to upload videos, manage playlists and subscriptions, update channel settings, and more. >If not, then there's really not much anyone can do about it. If their API is unusable, then follow the steps in the documentation, only let a computer do it. Use OAuth to authenticate with the service, access user's content that may be public, private, or unlisted. On a user operation, say move videos from one account to the other, in the backend: download the videos to temporary files using a third party tool that I will not mention here, then upload them to the new account. If you want to skimp, mount the user's Google Drive account to store the videos temporarily (as a buffer), and then from their Google Drive to their YouTube account. This way you don't pay for storage and are scalable right off the bat. Then build everything on top of Google App Engine : D Except you'll have a harder time doing the mount operations if you're on GAE, I suppose. So you only receive requests, mount Google Drives, download videos there, then the videos to the user's account/channel. Yes, you could eventually use something "in-memory", but if you have a lof of requests, you'll have to account for that RAM, hence using the user's Google Drive account. Again, I'm thinking of this off the top of my head, but I think it checks out. The user only has to select the videos from the source, and choose a destination, click OK, done. Go for coffee or something, instead of downloading them and good luck for people with crappy internet to do that. Future versions may enable you to do CRUD on the videos on a usable interface, not like the Studio thing. Display accounts and channels and playlists like folders and move videos around like you'd do on a file explorer, etc. I may do that once to transfer my videos. Your bio is "Serial Side Project Maker"... :P