Can you PLEASE have mercy on us and revert, at least temporarily, so we can use OAuth2 with 32 character codes, so that our entire existing install base isn't destroyed?
At this point, we might have to give up our entire business.
It's just not possible for us to start entirely from scratch -- after more than six months of downloads of our applications -- hundreds of thousands of installed users -- there's simply no way for us to communicate with our user base and make them all download and update new apps today.
Jeffery, please have some mercy on us here.
I feel like we are (inadvertently) being punished for "doing the right thing" and using Oauth2 instead of the old "Client Login" used by applications like iMovie and etc., which have not been affected by this change.
Have we basically killed ourselves by trying use OAuth2? Should we just give up entirely?
Or is OAuth2 basically doomed anyway and we should throw in the towel and make one more stab at distributing our app with the "Client Login" system?
Please help!!!!
regards
--
You received this message because you are subscribed to the Google Groups "YouTube APIs Developer Forum" group.
To view this discussion on the web visit https://groups.google.com/d/msg/youtube-api-gdata/-/5dms6ReT4poJ.
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.
No comments:
Post a Comment