将 OAuth 或公钥 API 用于私人 YouTube 应用程序? [英] Use OAuth or Public Key API for private YouTube application?

问题描述

我想使用 PHP 创建一个应用程序，该应用程序仅对我的 YouTube 帐户/频道进行身份验证，以创建播放列表、上传和播放将设置为私人的视频/播放列表.目前，用户不会登录自己的 YouTube 帐户，我的应用程序也不会访问他们的信息.

I would like to create an application using PHP that would authenticate to only my YouTube account/channel to create playlists, upload and play videos/playlists which would be set to Private. For now, users will not be logging into their own YouTube accounts and my application will not access their information.

我应该使用 OAuth 还是公钥 API?各自的优缺点是什么?

Should I use OAuth or the Public Key API? What are the advantages and disadvantages of each?

用户是否有必要与 OAuth 交互?

Is it necessary that the user interacts with OAuth?

如果应用程序位于共享托管 Web 服务器(许多客户具有相同的 IP 地址)上，则公钥有什么含义?

What are the implications with the Public Key if the application is on a shared hosting web server (many customers having the same IP address)?

推荐答案

如果您想访问或修改任何私有数据，例如，您必须使用 OAuth.上传视频.

You must use OAuth if you want to access or modify any private data, e.g. upload videos.

毕竟，您是必须代表您的帐户授权远程访问的(一个)用户.

After all, you are the (one) user who has to authorize remote access on behalf of your account.

API 密钥仅用于检索公共数据，在您的情况下不会让您走得更远.

API Keys are only used for retrieving public data and wouldn't get you far in your case.

只要您使用指定的网址(例如mydomain.net/myyoutubeapp")，共享托管网络服务器就不会出现任何问题.

As long as you use your designated url (e.g. 'mydomain.net/myyoutubeapp), there won't be any problems on a shared hosting web server.

这篇关于将 OAuth 或公钥 API 用于私人 YouTube 应用程序?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！