Change Details

Because the video loader has ffprobe/ffmpeg pointed directly at https URLs of objects stored in swift, it doesn't support authentication, which is required for files stored in temp folders. Ideally we would auth into swift when dealing with temp URLs and pass the required cookies/headers to the ffprobe/ffmpeg commands. Or we just don't care about thumbnailing video files still in temp storage... nobody has complained about them in 7 months.

Because the video loader has ffprobe/ffmpeg pointed directly at https URLs of objects stored in swift, it doesn't support authentication, which is required for files stored in temp folders. Ideally we would auth into swift when dealing with temp URLs and pass the required cookies/headers to the ffprobe/ffmpeg commands.

Because the video loader has ffprobe/ffmpeg pointed directly at https URLs of objects stored in swift, it doesn't support authentication, which is required for files stored in temp folders. Ideally we would auth into swift when dealing with temp URLs and pass the required cookies/headers to the ffprobe/ffmpeg commands. Or we just don't care about thumbnailing video files still in temp storage... nobody has complained about them in 7 months.