[YouTube-API] Re: Installed Application Developers - What Upload Method Do You Use?

Hello Dan,

AuthSub, ClientLogin, and OAuth 1 are all deprecated:

http://googledevelopers.blogspot.com/2012/04/changes-to-deprecation-policies-and-api.html

They definitely aren't going away tomorrow, and they remain the
options that are best-supported in our client libraries for the time
being, but I would strongly recommend OAuth 2 for all new development
at this point.

I think you're being a little harsh on OAuth 2 after being bitten by
the issue that's been thoroughly hashed out at

https://groups.google.com/group/youtube-api-gdata/browse_thread/thread/08ed01bfc1fff877#

Cheers,
-Jeff Posnick, YouTube API Team
groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |
@YouTubeDev

On Apr 24, 12:46 pm, Dan S <dsie...@gmail.com> wrote:
> Greetings,
>
> Out of:
> AuthSub
> oAuth 1.0
> oAuth 2.0
> ClientLogin
>
> What do all of you use and why?
>
> I had up until recently used oAuth 2.0, but an overnight change in the way
> YouTube delivers their auth tokens broke my entire install base.
>
> How is everyone else doing their uploads so that you are not at the mercy
> of YouTube's unannounced changes? I'd like to adapt my app if I can, but I
> need to do whatever everyone else is doing that "just works" or is most
> immune to unannounced API behavior.

--
You received this message because you are subscribed to the Google Groups "YouTube APIs Developer Forum" group.
To post to this group, send email to youtube-api-gdata@googlegroups.com.
To unsubscribe from this group, send email to youtube-api-gdata+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/youtube-api-gdata?hl=en.