@erozas Before making a decision I have done some testing today, I have generated a new app on Vimeo API and a valid token to be used on my development server. I have uploaded a couple of videos and, even if I cannot still upload anything for the three business days delay I guess (this is what Vimeo says on FAQ), I can request all the videos and get the json ready to be parsed, the problem is that all the videos on Vimeo must be private (and they are right now), but they cannot be seen by the user. If I render a view that simply parse the
Vimeo::request('/me/videos', ['per_page' => 10], 'GET');
and I echo the $data['body']['data'][index]['embed']['html']
Vimeo ask the user to log in in order to view theme, while I wish Vimeo use the token (and they use it because if I delete it an exception will be thrown) to use my user as the login user, and not ask the visitor to have a Vimeo account, and even if the visitor has an account he won't see anything because of the private video.
Here in laracast all the video must be private in order to not be visibile without subscription, but laracast does not ask me to log in to vimeo in order to watch videos...so there is some concept I am missing I guess. Have you ever faced a situation like this? I thought that using the vimeo token would let the app "been seen" by Vimeo as the Vimeo user associated with the token...but I am wrong... @JeffreyWay maybe knows something about all this stuff ;)