Youtube-dl (Forbidden 403 error, not a common solution) - youtube-dl

I am using youtube-dl for downloading videos from youtube mostly. It is latest version on my Mac.
This time I wanted to download some video presentation from conference I am participating. They are using zoom client in Chrome browser.
I am not able to download video with presentation
I used the following steps:
There are two video streams on the same webpage (one for presenter, one for presentation material)
youtube-dl captures only first part with presenter view.
There are no other information from json file about second video (no playlist, no other ids).
I used another software to download a video (VideoDuke).
It shows that there are two videos with different size (presenter and presentation).
I am forbidden to download both of them (youtube-dl could download the first one, by use original URL).
I can copy video address from VideoDuke and use it for youtube-dl.
I receive error "Forbidden 403" with youtube-dl on both of videos (different links from original URL).
--rm-cache-dir does not help.
if I use --verbose on original URL, I can see that it is invoking downloader on the first video with the same URL the VideoDuke produced, and it can download the file.
Is it possible to invoke downloader on the second URL provided by VideoDuke. I can also get similar URL from inspector in Google Chrome.
Last year I participated in the same conference and the original URL was similar, although that time there were some true/false statements I could tweak and download exactly the presentation video, and not the presenter. This year, that option disappeared.

Related

Vimeo API not returning a full page of results

I'm using the Vimeo API to get paged data on my videos. I'm using the per_page and page parameters like so:
https://api.vimeo.com/me/videos?page=4&per_page=8
However, some of the pages of results do not contain 8 videos. For example my 4th page of results is only returning 6 results, yet page 5 has a full set, and there's many more pages. So it's not like I've ran out of videos.
I've checked the video's privacy settings and can't see any differences between the videos that are showing and the videos I'd expect to show on that page that aren't. I've tried setting a sort direction and that didn't help. I've also used the query parameter to search for the videos I think are not showing at they are being returned if I seach for them directly.
Also my auth token scope includes Public, Private and Video Files
I got in contact with Vimeo support. It's due to an issue on their and they have told me they are releasing a fix on the 21st of Feb 2023. In the meantime adding this parameter to the request is a workaround but this will be removed soon.
&include_disabled_by_min_tier=true

Video unavailable when loading from Azure Video Indexer API

I am having problems with indexing a video, If I try to load a video with a URL from the Azure media service, Video Indexer throws error and abruptly fails indexing with error message "Video Unavailable", this happens if I load it with the API or directly in videoindexer.ai, does anyone have any idea how I can fix this problem?
Video Indexer (VI) expect to have a direct URL for the video itself. So, when you put the URL in your browser the video should start download/play
Can you please elaborate more about how you generate the URL in Azure Media Services (AMS)? For example, are you using a ClearStreamingOnly or DownloadAndClearStremaing locator AMS Streaming Locators?
You should be using the DownloadAndClearStremaing and use the generated video download URL.
Another option will be, as you already have your video in AMS, then it is saved in the AMS linked storage, you can generate a SAS Url for the video file and give that to VI to index.

Og:image not showing in FB debugger but link is ok

I have a very very strange problem. I use a WordPress website to publish a picture every day, and of course, I want to publish it on my facebook page.
I've tried with Open Graph informations from Yoast, or from Jetpack and both but the problem is the same : no picture to show on social networks! Not a good thing for pictures based website ;-)
I've tried Open Graph debugger and when I look at this, I have a good link to my image on og:image property... but the picture doesn't display. It's a transparent picture to click that open the good image in a new link, but can't publish it on social networks.
You can try with this adress : http://social.1max2peche.com/belle-boule-de-mucus/
Put in the image URL directly (in the browser): http://www.1max2peche.com/design/magazine-peche-1max2peche-logo.png
Happens to at least 2 out of 3 images in the og:image tags, and it may be the problem. Also take a look at the image specifications: https://developers.facebook.com/docs/sharing/best-practices#images
You see that it redirects, so of course Facebook cannot get it. Make sure to check out your rewrite stuff.

The Facebook Graph API does not include videos in wall posts

I'm using the Graph API to read some wall posts from a Facebook group. I get an array with post objects containing the expected information except for one entry with the type "status" which is a posted video.
But I do not get any information about the video. There is no difference between a default text-only post. How can I access the video URL, thumbnail, etc.?
Edit:
The video is a "native" facebook video. I do not fully understand the various types of posts. When you post a plain url facebook grabs the meta information and displays them properly. But it seems this is not included in the api output.
Where are the differences between shared contens, status updates including urls and status updates with photos or videos?

me/feed with pic from different domain

I was trying to find this on facebook's site in their documentation but so far no luck. I'm sure others must have run into this before.
I use Amazon S3 for storing images. I didn't know ahead of time that if I named my bucket as my domain name with subdomain I could link that way, so until I move all of the pictures I have to link to mybucket.s3.amazonaws.com domain. When I include a picture from there with a post to the wall the picture doesn't show up. If I change the picture to one on the server itself the picture does show up. It seems that the domain name of the picture must match my app? I looked at bugzilla and didn't see this mentioned. Facebook's forum says to post questions here.
I'm using the C# Facebook SDK from CodePlex.
My code looks like (with error handling and authentication check removed):
var client = new FacebookClient(FACEBOOK_APP_ID, FACEBOOK_SECRET);
client.AccessToken = facebook.AccessToken;
var parameters = new Dictionary<string, object>();
parameters.Add("name", name);
parameters.Add("caption", title);
parameters.Add("message", message);
parameters.Add("link", link);
parameters.Add("source", link);
parameters.Add("picture", imageUrl);
client.Post("me/feed", parameters);
I verified that imageUrl does indeed have a correct picture, the domain name just doesn't match. The picture on amazon s3 has public read access. I can view it from my browser so I don't think it's a permission problem. I've tried a few different pictures with the same problem. Only time it's worked so far is when the picture was on the server itself.
So, my question is, is it a problem with me, or does facebook block images that don't match the domain name specified on the app?
You can upload the picture from that url, then add its object id in the post.
Refer to: http://developers.facebook.com/blog/post/526/?ref=nf
Uploading Photos to the Graph API via a URL
Earlier this year, we released support for uploading photos directly
via the Graph API. This requires sending the photo as a MIME-encoded
form field. We are now enhancing our photo upload capability by
introducing the ability to upload photos simply by providing a URL to
the image. This simplifies photo management for a number of use cases:
App developers who host their images on Amazon S3 or a similar
service can pass the S3 URL directly to Facebook without having to
download the file to their application servers only to upload it
again to Facebook. This improves performance and reduces costs for
developers.
Apps written on platforms that don't have good support for
multipart file uploads can create new photos more easily.
To upload a photo via a URL, simply issue an HTTP POST to
ALBUM_ID/photos with the url field set to the URL of the photo you
wish to upload. You need the publish_stream permission to perform this
operation. You can also include an optional message parameter to set a
caption for the photo.
I'am facing the same issue as well. Based on my observations it seems that facebook does not like it when the picture url has more than one sub-domain.
I tried the below 2 URL variations for the same image..
mybucket.s3.amazonaws.com - throws an error
s3.amazonaws.com/mybucket - works fine
:picture => 'http://mybucket.s3.amazonaws.com/footprints/15/coverimgs/medium.jpg'
OAuthException: (#100) picture URL is not properly formatted
:picture => 'http://s3.amazonaws.com/mybucket/footprints/15/coverimgs/medium.jpg'
{"id"=>"587472956_10150280873767957"}
Now i have to figure out how to change the URL structure for the image while passing it to the FB graph API.
I would log it as a bug. If this is really the case, which I kinda doubt, you could create a 301 redirect on your own domain for each image that redirects to the Amazon url.